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 1705899 - glibc: Backport libio vtable validation improvements [rhel-7.6.z]
Summary: glibc: Backport libio vtable validation improvements [rhel-7.6.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.7
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Florian Weimer
QA Contact: Sergey Kolosov
URL:
Whiteboard:
Depends On: 1595191
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-03 07:48 UTC by RAD team bot copy to z-stream
Modified: 2022-03-13 17:05 UTC (History)
15 users (show)

Fixed In Version: glibc-2.17-260.el7_6.6
Doc Type: Bug Fix
Doc Text:
Cause: libio vtable validation is a security hardening technique that aims to make it harder for attackers to injection libio vtables and functions pointers after exploiting a memory corruption vulnerability. However, some old i386 applications do supply their own vtables, so the validation needs to be disabled, and the original implementation did not do this for interposed stdio handles. Consequence: Some old applications would fail with an error message, `Fatal error: glibc detected an invalid stdio handle`. Fix: glibc now detects interposition of stdio handle data structures and disables vtable validation in that case. Result: Old applications which were impacted by this defect work again.
Clone Of: 1595191
Environment:
Last Closed: 2019-06-04 17:15:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1338 0 None None None 2019-06-04 17:15:55 UTC
Sourceware 23236 0 'P2' 'RESOLVED' 'Harden function pointers in _IO_str_fields' 2019-12-03 11:42:00 UTC
Sourceware 23313 0 'P2' 'RESOLVED' 'libio vtables validation and standard file object interposition' 2019-12-03 11:42:01 UTC

Description RAD team bot copy to z-stream 2019-05-03 07:48:05 UTC 
This bug has been copied from bug #1595191 and has been proposed to be backported to 7.6 z-stream (EUS).
Comment 4 Sergey Kolosov 2019-05-17 11:17:43 UTC 
Verified by upstream testsuite tests: libio/tst-vtables-interposed, libio/tst-vtables. Also verified with reproducer on x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=1595191#c1
Comment 6 errata-xmlrpc 2019-06-04 17:15:54 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/RHBA-2019:1338
Note You need to log in before you can comment on or make changes to this bug.