Bug 1190123 (CVE-2015-1209)
| Summary: | CVE-2015-1209 chromium-browser: use-after-free in DOM | ||
|---|---|---|---|
| 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: | jrusnack, rhel-process-autobot, tpopela, watson-tool-maintainers |
| 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: |
A flaw was found in the Document Object Model (DOM) component of the Chromium browser. A remote attacker could exploit this use-after-free vulnerability by tricking a user into visiting a specially crafted web page. Successful exploitation could allow the attacker to execute arbitrary code or cause a denial of service (DoS) by crashing the browser.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-31 05:52:01 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: | 1190153, 1190154 | ||
| Bug Blocks: | 1190126, 1205570 | ||
|
Description
Vasyl Kaigorodov
2015-02-06 12:04:25 UTC
Currently private upstream bug: https://code.google.com/p/chromium/issues/detail?id=447906 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/. |