Enterprise Linux Desktop SupplementaryOperating system · Redhat
CVE-2014-3192
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA use-after-free vulnerability in the ProcessingInstruction::setXSLStyleSheet function in Blink's DOM implementation allows remote attackers to potentially execute arbitrary code or cause denial of service by exploiting memory corruption when processing malicious XSL stylesheets through the ProcessingInstruction API.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise Linux Desktop SupplementaryOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 6.0
Enterprise Linux Server Supplementary EusOperating system
= 6.6.z
Enterprise Linux Workstation SupplementaryOperating system
= 6.0
SafariWeb browser
= 6.2.2= 7.1.2= 8.0.2
ChromeWeb browser
<= 38.0.2125.7<= 12.1.3<= 8.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionNavigate to chrome://settings/help or type 'chrome://version' in the address bar to view the installed Chrome versionAffected if Version is 38.0.2125.7 or lower (the installed version is <= 38.0.2125.7)
-
Check Apple Safari versionOpen Safari, then go to Safari > About Safari to view the version numberAffected if Version matches 6.2.2, 7.1.2, or 8.0.2 exactly, or is lower than these listed versions
-
Check Apple iTunes versionOpen iTunes and navigate to Help > About iTunes to view the versionAffected if Version is 12.1.3 or lower
-
Check iOS version on iPhone/iPadGo to Settings > General > About on the device to view the iOS versionAffected if Version is 8.1.2 or lower
-
Check Red Hat Enterprise Linux 6.x browser packagesQuery the installed package version using rpm -qa | grep -i chromium or rpm -qa | grep -i webkit for RHEL 6.0 through 6.6Affected if The browser-related packages are at the vulnerable RHEL 6.0 through 6.6.z versions listed in the affected products
You are affected if any of the following are true: Chrome version is 38.0.2125.7 or lower, Safari is 6.2.2/7.1.2/8.0.2 or lower, iTunes is 12.1.3 or lower, iOS is 8.1.2 or lower, or RHEL 6.x browser packages match the listed vulnerable versions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Google Chrome to version 38.0.2125.101 or later to patch the vulnerability. Organizations should ensure browser update policies are enforced and consider disabling XSL processing if not required.
Fix this in Enterprise Linux Desktop Supplementary
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-3192 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data