Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1196745 - (CVE-2011-5320) CVE-2011-5320 glibc: scanf implementation crashes on certain inputs
CVE-2011-5320 glibc: scanf implementation crashes on certain inputs
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20110122,reported=2...
: Security
Depends On:
Blocks: 1188240 1196746
  Show dependency treegraph
 
Reported: 2015-02-26 11:13 EST by Vasyl Kaigorodov
Modified: 2018-02-08 09:47 EST (History)
10 users (show)

See Also:
Fixed In Version: glibc 2.15
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-07 23:00:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Sourceware 13138 None None None Never

  None (edit)
Description Vasyl Kaigorodov 2015-02-26 11:13:27 EST
It was reported [1] that scanf and related functions are crashing due to a bug [2] in glibc.

[1]: http://seclists.org/oss-sec/2015/q1/686
[2]: https://sourceware.org/bugzilla/show_bug.cgi?id=13138
Comment 1 Huzaifa S. Sidhpurwala 2015-07-17 01:55:58 EDT
Statement:

This issue affects the version of glibc package as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Low security impact. A future update in Red Hat Enterprise Linux 6 may address this issue. This issue did not affect the versions of glibc as shipped with Red Hat Enterprise Linux 7.

Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates.

Note You need to log in before you can comment on or make changes to this bug.