Bug 1165655 (CVE-2014-7906)

Summary: CVE-2014-7906 chromium-browser: Use-after-free in pepper plugins
Product: [Other] Security Response Reporter: Vasyl Kaigorodov <vkaigoro>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: fedora, huzaifas, jgrulich, jreznik, jrusnack, kalevlember, kevin, kevin, ltinkl, martin.sourada, mclasen, mtasaka, rdieter, rnovacek, than, tpopela
Target Milestone: ---Keywords: Reopened, Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Chrome 39.0.2171.65 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-25 04:47:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1165942, 1165943    
Bug Blocks: 1165665    

Description Vasyl Kaigorodov 2014-11-19 12:49:47 UTC
Unspecified use-after-free vulnerability has been found [1] in Chromium pepper plugins.

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

External References:

http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html

Comment 2 Huzaifa S. Sidhpurwala 2014-11-20 05:38:18 UTC
Statement:

(none)

Comment 4 Huzaifa S. Sidhpurwala 2014-11-20 14:12:47 UTC
I dont have access to the upstream bug. However it seems this is related to 

https://chromium.googlesource.com/chromium/src/+/db8e2abccd737b0513a2cd11add50b543783f2da

Tomas, confirmed this is a part of the code we ship, calling it affected.

Comment 5 errata-xmlrpc 2014-11-24 20:57:23 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 6 Kevin Kofler 2015-08-19 20:45:52 UTC
Why were we Qt/KDE maintainers put on CC for this bug? This is clearly a Chromium-specific vulnerability that cannot possibly affect QtWebKit or KHTML (because neither supports Pepper plugins). Only QtWebEngine can possibly be affected, but it is not currently in Fedora.