Bug 1165656 (CVE-2014-7907) - CVE-2014-7907 chromium-browser: Use-after-free in blink
Summary: CVE-2014-7907 chromium-browser: Use-after-free in blink
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2014-7907
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1165942 1165943
Blocks: 1165665 1205570
TreeView+ depends on / blocked
 
Reported: 2014-11-19 12:52 UTC by Vasyl Kaigorodov
Modified: 2021-02-17 05:59 UTC (History)
1 user (show)

Fixed In Version: Chrome 39.0.2171.65
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-31 05:52:30 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:1894 0 normal SHIPPED_LIVE Important: chromium-browser security update 2014-11-25 01:56:55 UTC

Description Vasyl Kaigorodov 2014-11-19 12:52:24 UTC 
Unspecified use-after-free vulnerability was found in blink (the rendering engine used by Chromium).

[1]: https://code.google.com/p/chromium/issues/detail?id=424453

External references:

http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html
Comment 3 Huzaifa S. Sidhpurwala 2014-11-21 05:13:27 UTC 
The upstream bug is closed, but this seems to be the commit which fixes the issue:

https://src.chromium.org/viewvc/blink?revision=184185&view=revision
Comment 4 errata-xmlrpc 2014-11-24 20:57:26 UTC 
This issue has been addressed in the following products:

  Supplementary for Red Hat Enterprise Linux 6

Via RHSA-2014:1894 https://rhn.redhat.com/errata/RHSA-2014-1894.html
Comment 5 Huzaifa S. Sidhpurwala 2015-07-31 05:43:30 UTC 
Statement:

This issue affects the versions of webkitgtk and webkitgtk3 as shipped with Red Hat Enterprise Linux 6 and 7 respectively.

Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
Note You need to log in before you can comment on or make changes to this bug.