Bug 1185220 (CVE-2014-7940) - CVE-2014-7940 ICU: uninitialized value use in the collation component
Summary: CVE-2014-7940 ICU: uninitialized value use in the collation component
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2014-7940
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1185236
Blocks: 1185232 1186680
TreeView+ depends on / blocked
 
Reported: 2015-01-23 09:05 UTC by Martin Prpič
Modified: 2021-02-17 05:45 UTC (History)
7 users (show)

Fixed In Version: Chrome 40.0.2214.91
Clone Of:
Environment:
Last Closed: 2015-12-17 10:40:59 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0093 0 normal SHIPPED_LIVE Important: chromium-browser security update 2015-01-27 23:46:28 UTC

Description Martin Prpič 2015-01-23 09:05:51 UTC 
An unspecified uninitialized-value flaw was found in the ICU component of the Chromium browser.

External References:

http://googlechromereleases.blogspot.com/2015/01/stable-update.html
Comment 1 Tomas Hoger 2015-01-23 12:50:52 UTC 
Google Chrome bug is:

https://code.google.com/p/chromium/issues/detail?id=433866

However, the bug is currently not public.  The following commits can be identified using the bug id:

https://chromium.googlesource.com/chromium/deps/icu/+/866ff696e9022a6000afbab516fba62cfa306075
https://chromium.googlesource.com/chromium/deps/icu/+/a626a75aad2675254073366fcaa9465dacf17100

Chrome README includes the following information about ICU upstream status of this issue:

   - No upstream bug filed because the upstream code was completely
     rewritten during the ICU 53 cycle.
Comment 2 errata-xmlrpc 2015-01-27 18:48:04 UTC 
This issue has been addressed in the following products:

  Supplementary for Red Hat Enterprise Linux 6

Via RHSA-2015:0093 https://rhn.redhat.com/errata/RHSA-2015-0093.html
Note You need to log in before you can comment on or make changes to this bug.