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 1135840 - (CVE-2012-6656) CVE-2012-6656 glibc: crash in IBM930 decoding
CVE-2012-6656 glibc: crash in IBM930 decoding
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20120523,repor...
: Security
Depends On:
Blocks: 1135843
  Show dependency treegraph
 
Reported: 2014-08-31 22:25 EDT by Murray McAllister
Modified: 2015-07-31 03:25 EDT (History)
9 users (show)

See Also:
Fixed In Version: glibc 2.16
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-08-31 22:26:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Murray McAllister 2014-08-31 22:25:22 EDT
A crash was found in the IBM930 decoding:

https://sourceware.org/bugzilla/show_bug.cgi?id=14134
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=6e230d11837f3a

Florian Weimer noted:

"...out-of-bounds reads at a fixed offset relative to the data segment of a DSO, and in all cases I've seen, they were right in the middle of an unmapped segment of the same DSO. This means that these bugs are just crashers, but they can still result in denial-of-service conditions."

This issue has been fixed in version 2.16. The fix is included in Fedora and Red Hat Enterprise Linux 5, 6, and 7.

Reference:

http://seclists.org/oss-sec/2014/q3/466

Statement:

Not vulnerable. This issue does not affect the versions of glibc in Red Hat Enterprise Linux 5, 6, or 7.
Comment 1 Murray McAllister 2014-09-02 02:04:08 EDT
MITRE assigned CVE-2012-6656 to this issue:

http://www.openwall.com/lists/oss-security/2014/09/02/1

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