Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 516749[details]
fuzzed binary dump
Description of problem:
I used fuzzing to create damaged binary dump. Fuzzing is a technique how to little bit damage any input file.
Version-Release number of selected component (if applicable):
dmidecode-2.10-1.30.1.el6.x86_64
python-dmidecode-3.10.13-1.el6.x86_64
How reproducible:
try to create specific binary dump
Steps to Reproduce:
1. have a nice binary dump
2. use fuzzing tool to damage it , see attached fuzzed.bin
3. cat script.py
import dmidecode
dmidecode.clear_warnings()
dmidecode.set_dev('fuzzed.bin')
x = dmidecode.dmidecodeXML()
x.SetResultType(dmidecode.DMIXML_DOC)
x.QuerySection('processor').saveFormatFileEnc('-','UTF-8',1)
4. python script.py
Segmentation fault (core dumped)
Actual results:
Segmentation fault (core dumped)
Expected results:
no segmentation fault, I would expect warning message
Additional info:
dmidecode --from-dump fuzzed.bin
# dmidecode is able to read such a file
fuzzing: used zzuf http://caca.zoy.org/wiki/zzuf
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6RHEL Program Management
2013-10-14 01:02:25 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
python-dmidecode-3.10.15-1.el6 manages to partially decode the corrupted dmi image dump, then provides a useful traceback with error messages about the DMI structures being wrong. I confirmed similar behavior with /usr/sbin/dmidecode.
The previous version of python-dmidecode would seg-fault while producing no output.
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://rhn.redhat.com/errata/RHBA-2017-0691.html