Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2012-6685

rubygem-nokogiri: XML eXternal Entity (XXE) flaw

Overview

Published
19 Feb 2020
Modified
21 Nov 2024
High CVE
1 Registry packages
202 OS packages
3 Linux distributions
Yes Fix available

Description

Nokogiri before 1.5.4 is vulnerable to XXE attacks

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-776

Affected packages · 1

Packages affected by CVE-2012-6685
EcosystemPackageVulnerableFixed in
RubyGems nokogiri <1.5.4 1.5.4

Open a package to see all its vulnerabilities.

Operating systems · 86 fixes

Red Hat 1 release · 81 packages

fixed 81
rubygem-unf-ext rubygem-memory-buffer rubygem-net-telnet bubblewrap python2-future rubygem-pg +75
Red Hat fixes for CVE-2012-6685
ReleasePackageFixed inAdvisory
7 rubygem-unf-ext +1 0:0.0.7.5-1.el7cf RHSA-2019:0212
7 rubygem-memory-buffer +1 0:0.1.0-2.el7cf RHSA-2019:0212
7 rubygem-net-telnet 0:0.1.1-90.el7cf RHSA-2019:0212
7 bubblewrap 0:0.1.7-1.el7 RHSA-2019:0212
7 python2-future 0:0.16.0-1.el7cf RHSA-2019:0212
7 rubygem-pg +1 0:0.18.4-2.el7cf RHSA-2019:0212

75 more rows

debian 4 releases · 1 package

fixed 4
ruby-nokogiri
debian fixes for CVE-2012-6685
ReleasePackageFixed in
11 ruby-nokogiri 1.5.4-1
12 ruby-nokogiri 1.5.4-1
13 ruby-nokogiri 1.5.4-1
14 ruby-nokogiri 1.5.4-1

echo 1 release · 1 package

fixed 1
ruby-nokogiri
echo fixes for CVE-2012-6685
ReleasePackageFixed in
ruby-nokogiri 1.5.4-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.