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.
There was a stack overflow caused by format string vulnerability in fmt_entry function of ncurses tool with latest verison(6.0). Crafted input could lead to arbitrary code execution.
Created attachment 1291519[details]
Triggered by "infotocp POC6"
Description of problem:
In the fmt_entry function line 835, the sprintf function was called for copy some values related to input for the buffer that exceeding the length of MAX_TERMINFO_LENGTH + EXTRA_CAP bytes. The buffer out of bound written led to the return address of fmt_entry function was covered.
Version-Release number of selected component (if applicable):
<=6.0
How reproducible:
infotocap $POC
Steps to Reproduce:
1. gdb infotocap
2. set breakpoint for fmt_entry return address before calling sprintf and after calling sprintf
3. check the ret address be covered
Actual results:
the fmt_entry ret address be covered
crash
Expected results:
the fmt_entry ret address be covered
crash
Additional info:
Credits:
This vulnerability is detected by team OWL337, with our custom fuzzer coll AFL. Please contact ganshuitao and chaoz.cn if you need more info about the team, the tool or the vulnerability.
Created attachment 1291519 [details] Triggered by "infotocp POC6" Description of problem: In the fmt_entry function line 835, the sprintf function was called for copy some values related to input for the buffer that exceeding the length of MAX_TERMINFO_LENGTH + EXTRA_CAP bytes. The buffer out of bound written led to the return address of fmt_entry function was covered. Version-Release number of selected component (if applicable): <=6.0 How reproducible: infotocap $POC Steps to Reproduce: 1. gdb infotocap 2. set breakpoint for fmt_entry return address before calling sprintf and after calling sprintf 3. check the ret address be covered Actual results: the fmt_entry ret address be covered crash Expected results: the fmt_entry ret address be covered crash Additional info: Credits: This vulnerability is detected by team OWL337, with our custom fuzzer coll AFL. Please contact ganshuitao and chaoz.cn if you need more info about the team, the tool or the vulnerability.