CVE-2014-3192
What it is
Use-after-free vulnerability in the ProcessingInstruction::setXSLStyleSheet function in core/dom/ProcessingInstruction.cpp in the DOM implementation in Blink, as used in Google Chrome before 38.0.2125.101, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 1.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.8% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 1.8% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Redhat Enterprise Linux Desktop Supplementary 6.0
- Redhat Enterprise Linux Server Supplementary 6.0
- Redhat Enterprise Linux Server Supplementary Eus 6.6.z
- Redhat Enterprise Linux Workstation Supplementary 6.0
- Apple Itunes ≤ 12.1.3
- Apple Safari 6.2.2
- Apple Safari 7.1.2
- Apple Safari 8.0.2
Attack profile CVSS 2.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2014-3192.md and follow it. Check whether this project is affected by CVE-2014-3192. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html
- http://lists.apple.com/archives/security-announce/2015/Jan/msg00000.html
- http://lists.apple.com/archives/security-announce/2015/Jan/msg00001.html
- http://lists.apple.com/archives/security-announce/2015/Jan/msg00002.html
- http://lists.apple.com/archives/security-announce/2015/Jun/msg00006.html
- http://rhn.redhat.com/errata/RHSA-2014-1626.html
- http://support.apple.com/HT204243
- http://support.apple.com/HT204245
- http://support.apple.com/HT204246
- http://www.securityfocus.com/bid/70273
- http://www.securitytracker.com/id/1031647
- https://crbug.com/403276
- https://src.chromium.org/viewvc/blink?revision=182309&view=revision
- https://support.apple.com/kb/HT204949
- http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html
- http://lists.apple.com/archives/security-announce/2015/Jan/msg00000.html
- http://lists.apple.com/archives/security-announce/2015/Jan/msg00001.html
- http://lists.apple.com/archives/security-announce/2015/Jan/msg00002.html
- http://lists.apple.com/archives/security-announce/2015/Jun/msg00006.html
- http://rhn.redhat.com/errata/RHSA-2014-1626.html
- http://support.apple.com/HT204243
- http://support.apple.com/HT204245
- http://support.apple.com/HT204246
- http://www.securityfocus.com/bid/70273
- http://www.securitytracker.com/id/1031647