Bug 1190158 (CVE-2015-1212)
Summary: | CVE-2015-1212 chromium-browser: various security fixes in Chrome 40.0.2214.111 | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Vasyl Kaigorodov <vkaigoro> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | tpopela |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Chrome 40.0.2214.111 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-31 05:52:10 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: | |||
Bug Blocks: | 1190126, 1205570 |
Description
Vasyl Kaigorodov
2015-02-06 14:13:08 UTC
Upstream bug is: https://code.google.com/p/chromium/issues/detail?id=455225 which references these bugs for real fixes: High severity: https://code.google.com/p/chromium/issues/detail?id=451918 https://code.google.com/p/chromium/issues/detail?id=451684 https://code.google.com/p/chromium/issues/detail?id=446459 https://code.google.com/p/chromium/issues/detail?id=445679 https://code.google.com/p/chromium/issues/detail?id=438365 https://code.google.com/p/chromium/issues/detail?id=427303 All above bugs are currently non-public. This issue has been addressed in the following products: Supplementary for Red Hat Enterprise Linux 6 Via RHSA-2015:0163 https://rhn.redhat.com/errata/RHSA-2015-0163.html 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/. |