RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1446765 - lshw html output does not escape the ampersand character
Summary: lshw html output does not escape the ampersand character
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lshw
Version: 7.4
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Petr Oros
QA Contact: Mike Gahagan
URL:
Whiteboard:
Depends On:
Blocks: 1472889
TreeView+ depends on / blocked
 
Reported: 2017-04-28 20:10 UTC by Mike Gahagan
Modified: 2019-02-15 03:10 UTC (History)
1 user (show)

Fixed In Version: lshw-B.02.18-9.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 10:03:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0689 0 None None None 2018-04-10 10:03:48 UTC

Description Mike Gahagan 2017-04-28 20:10:38 UTC 
Description of problem:
:: [  BEGIN   ] :: Running lshw and logging html output :: actually running 'lshw -html > /mnt/testarea/check-output/logs/lshw.out.html'
:: [   PASS   ] :: Running lshw and logging html output (Expected 0, got 0)
:: [  BEGIN   ] :: Validating html output :: actually running 'xmllint --html --noout /mnt/testarea/check-output/logs/lshw.out.html'
/mnt/testarea/check-output/logs/lshw.out.html:1551: HTML parser error : htmlParseEntityRef: no name
: </td><td class="second">Integrated Lights-Out Standard Slave Instrumentation &
                                                                               ^
/mnt/testarea/check-output/logs/lshw.out.html:1963: HTML parser error : htmlParseEntityRef: no name
">product: </td><td class="second">Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 &

offending line:
   1551                 <tr><td class="first">product: </td><td class="second">Integrated Lights-Out Sta   
   1551 ndard Slave Instrumentation & System Support</td></tr>
                                   ^^^

relevant entries still render in Firefox but fails xmllint's html validator.


Version-Release number of selected component (if applicable):

lshw-B.02.18-4.el7.x86_64

How reproducible:
always, depending on the hardware

Steps to Reproduce:
1. run lshw -html on a system with a hardware description field that contains an ampersand.
2.
3.

Actual results:
ampersand character is not escaped 

Expected results:
should escape the literal ampersand '&' with &amp for html compliance.


Additional info:
Comment 5 Mike Gahagan 2017-12-04 19:17:39 UTC 
This issue is fixed in lshw-B.02.18-9.el7:

               <tr><td class="first">product: </td><td class="second">Integrated Lights-Out Standard Slave Instrumentation &amp; System Support</td></tr>

                                        ^^^^^^^^

:: [   LOG    ] :: Package lshw is present
:: [   LOG    ] :: Package versions:
:: [   LOG    ] ::   lshw-B.02.18-9.el7.x86_64
:: [   PASS   ] :: Check to see if beaker lshw is not installed (Expected 0, got 0)
:: [   PASS   ] :: Getting lshw version information (Expected 0, got 0)
:: [   PASS   ] :: Getting lshw command line help information (Expected 0, got 0)
:: [   PASS   ] :: Running lshw with no options and logging output (Expected 0, got 0)
:: [   PASS   ] :: Running lshw and logging sanitized output (Expected 0, got 0)
:: [   PASS   ] :: Checking that sensitive information is removed from sanitized output (Expected 0, got 0)
:: [   PASS   ] :: Generating diff of unsanitized and sanitized output (Expected 0,1, got 1)
:: [   PASS   ] :: Running lshw and logging html output (Expected 0, got 0)
:: [   PASS   ] :: Validating html output (Expected 0, got 0)
:: [   PASS   ] :: running lshw and logging xml output (Expected 0, got 0)
:: [   PASS   ] :: Validating xml output (Expected 0, got 0)
:: [   PASS   ] :: Running lshw and logging json output (Expected 0, got 0)
:: [   PASS   ] :: Validating json output (Expected 0, got 0)
:: [   PASS   ] :: Running lshw and logging sql output (Expected 0, got 0)
:: [   PASS   ] :: Validating sql output (Expected 0, got 0)
:: [   LOG    ] :: Duration: 23s
:: [   LOG    ] :: Assertions: 15 good, 0 bad
:: [   PASS   ] :: RESULT: Test
Comment 8 errata-xmlrpc 2018-04-10 10:03:13 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0689
Note You need to log in before you can comment on or make changes to this bug.