CVE-2012-2893: Double free vulnerability in libxslt, as used in Google Chrome before 22.0.1229.79, allows remote attackers to cause a denial of service or…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 74.3% of all records.
- Fixed version: libxslt (Debian:12) 1.1.26-14; libxslt (Debian:6.0) 1.1.26-6+squeeze2; libxslt (Red Hat:enterprise_linux:5::client) 0:1.1.17-4.el5_8.3.
Low priority for now. Upgrade to libxslt (Debian:12) 1.1.26-14; libxslt (Debian:6.0) 1.1.26-6+squeeze2; libxslt (Red Hat:enterprise_linux:5::client) 0:1.1.17-4.el5_8.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Double free vulnerability in libxslt, as used in Google Chrome before 22.0.1229.79, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to XSL transforms.
- Published
- Sep 26, 2012
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 74th percentile
- CWE
- CWE-399
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| chrome | cpe:2.3:a:google:chrome |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- google chromeup to 22.0.1229.78 inclusive
- google chrome22.0.1229.0
- google chrome22.0.1229.1
- google chrome22.0.1229.10
- google chrome22.0.1229.11
- google chrome22.0.1229.12
- google chrome22.0.1229.14
- google chrome22.0.1229.16
+12 more rows
- google chrome22.0.1229.17
- google chrome22.0.1229.18
- google chrome22.0.1229.2
- google chrome22.0.1229.20
- google chrome22.0.1229.21
- google chrome22.0.1229.22
- google chrome22.0.1229.23
- google chrome22.0.1229.24
- google chrome22.0.1229.25
- google chrome22.0.1229.26
- google chrome22.0.1229.27
- google chrome22.0.1229.28
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libxslt | before 1.1.26-14 | 1.1.26-14 |
| Debian:6.0 | libxslt | before 1.1.26-6+squeeze2 | 1.1.26-6+squeeze2 |
| Red Hat:enterprise_linux:5::client | libxslt | before 0:1.1.17-4.el5_8.3 | 0:1.1.17-4.el5_8.3 |
| Red Hat:enterprise_linux:5::client | libxslt-debuginfo | before 0:1.1.17-4.el5_8.3 | 0:1.1.17-4.el5_8.3 |
| Red Hat:enterprise_linux:5::client | libxslt-python | before 0:1.1.17-4.el5_8.3 | 0:1.1.17-4.el5_8.3 |
| Red Hat:enterprise_linux:5::client_workstation | libxslt-devel | before 0:1.1.17-4.el5_8.3 | 0:1.1.17-4.el5_8.3 |
| Red Hat:enterprise_linux:6::client | libxslt | before 0:1.1.26-2.el6_3.1 | 0:1.1.26-2.el6_3.1 |
| Red Hat:enterprise_linux:6::client | libxslt-debuginfo | before 0:1.1.26-2.el6_3.1 | 0:1.1.26-2.el6_3.1 |
| Red Hat:enterprise_linux:6::client | libxslt-devel | before 0:1.1.26-2.el6_3.1 | 0:1.1.26-2.el6_3.1 |
| Red Hat:enterprise_linux:6::client | libxslt-python | before 0:1.1.26-2.el6_3.1 | 0:1.1.26-2.el6_3.1 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4863Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of…KEV95Now
- CVE-2021-21224Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a…KEV90Now
- CVE-2018-17463Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 allowed a remote attacker to execute arbitrary code inside a…KEV90Now
Published before and after this one in the same product
- ← EarlierCVE-2012-2891Sep 26, 2012 · The IPC implementation in Google Chrome before 22.0.1229.79 allows attackers to obtain potentially sensitive information about memory…20Monitor
- ← EarlierCVE-2012-2892Sep 26, 2012 · Unspecified vulnerability in Google Chrome before 22.0.1229.79 allows remote attackers to bypass the pop-up blocker via unknown vectors.20Monitor
- Later →CVE-2012-2894Sep 26, 2012 · Google Chrome before 22.0.1229.79 does not properly handle graphics-context data structures, which allows remote attackers to cause a…27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libxslt | 1.1.26-14 · Debian:12 | Package registry (OSV) |
| red hat:libxslt | 0:1.1.17-4.el5_8.3 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:libxslt-debuginfo | 0:1.1.17-4.el5_8.3 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:libxslt-devel | 0:1.1.17-4.el5_8.3 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:libxslt-python | 0:1.1.17-4.el5_8.3 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- googlechromereleases.blogspot.com/2012/09/stable-channel-update_25.html
- lists.opensuse.org/opensuse-security-announce/2012-10/msg00012.html
- secunia.com/advisories/50838
- www.debian.org/security/2012/dsa-2555
- www.mandriva.com/security/advisories?name=MDVSA-2012:164
- chromiumcodereview.appspot.com/10919019
- code.google.com/p/chromium/issues/detail?id=144799
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15714
- src.chromium.org/viewvc/chrome?view=rev&revision=154331
Vendor advisories and official records. Exploit/PoC links are deliberately left out.