CVE-2013-0333

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 95.3% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 96%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 96%CVSS v2: 7.5Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

lib/active_support/json/backends/yaml.rb in Ruby on Rails 2.3.x before 2.3.16 and 3.0.x before 3.0.20 does not properly convert JSON data to YAML data for processing by a YAML parser, which allows remote attackers to execute arbitrary code, conduct SQL injection attacks, or bypass authentication via crafted data that triggers unsafe decoding, a different vulnerability than CVE-2013-0156.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5HIGHlow confidence
EG Risk
76
EG Risk 76/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation95% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
96%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 30, 2013

Last Modified

April 29, 2026

References (22)

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrubygem-activesupport-1:3.0.10-9.el6cf2013-01-29redhat
redhatrubygem-activesupport-1:3.0.10-7.el6cf2013-01-28redhat
redhatrubygem-activesupport-1:3.0.13-4.el6op2013-01-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
rails—
  • every version up to 2.3.14.1: fixed in 2.3.14.1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rails—
  • every version up to 2.3.14.1: fixed in 2.3.14.1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rails—
  • every version up to 2.3.14.1: fixed in 2.3.14.1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rails—
  • every version up to 2.3.14.1: fixed in 2.3.14.1
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
rails2.3.5-1.2 ... 2.3.5-1.2+squeeze5 (8 versions)
  • every version up to 2.3.5-1.2+squeeze6: fixed in 2.3.5-1.2+squeeze6
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
activesupport3.0.0 ... 3.0.9.rc5 (36 versions)
  • 2.3.2 up to 2.3.16: fixed in 2.3.16
  • 3.0.0 up to 3.0.20: fixed in 3.0.20
—

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 0× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-01 04:40 UTCOSV refresh
  2. 2026-09-30 14:58 UTCEPSS rescore
  3. 2026-09-29 08:34 UTCEG score recompute
  4. 2026-09-24 13:57 UTCEPSS rescore
  5. 2026-09-18 19:21 UTCEPSS rescore
  6. 2026-09-15 03:04 UTCEPSS rescore
  7. 2026-09-12 07:10 UTCOSV refresh
  8. 2026-09-06 13:42 UTCEPSS rescore
  9. 2026-09-05 15:22 UTCEPSS rescore
  10. 2026-09-04 13:55 UTCEPSS rescore
  11. 2026-08-24 12:30 UTCOSV refresh
  12. 2026-08-24 07:23 UTCEPSS rescore
  13. 2026-08-16 02:09 UTCEPSS rescore
  14. 2026-08-08 08:19 UTCOSV refresh
  15. 2026-07-30 01:26 UTCEPSS rescore
  16. 2026-07-26 13:47 UTCEG score recompute▲ 7.50
  17. 2026-07-23 01:13 UTCVendor advisory
  18. 2026-07-23 01:11 UTCVendor advisory
  19. 2026-07-23 01:09 UTCEG score recompute▼ 9.00
  20. 2026-07-23 00:12 UTCEG score recompute
  21. 2026-07-22 21:51 UTCEG score recompute
  22. 2026-07-22 14:50 UTCOSV refresh
  23. 2026-07-19 14:27 UTCEPSS rescore
  24. 2026-07-19 14:27 UTCEPSS rescore
  25. 2026-07-19 02:25 UTCEPSS rescore
Show 28 more
  1. 2026-07-19 02:25 UTCEPSS rescore
  2. 2026-07-15 16:54 UTCEPSS rescore
  3. 2026-07-15 16:54 UTCEPSS rescore
  4. 2026-07-05 10:29 UTCOSV refresh
  5. 2026-07-04 06:27 UTCEPSS rescore
  6. 2026-06-16 21:13 UTCOSV refresh
  7. 2026-06-15 17:44 UTCEPSS rescore
  8. 2026-06-13 22:57 UTCEPSS rescore
  9. 2026-06-12 23:08 UTCEPSS rescore
  10. 2026-06-10 13:18 UTCEPSS rescore
  11. 2026-06-06 13:45 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-05-31 22:28 UTCEPSS rescore
  14. 2026-05-31 22:28 UTCEPSS rescore
  15. 2026-05-29 01:09 UTCEG score recompute
  16. 2026-05-29 01:09 UTCVendor advisory
  17. 2026-05-27 13:38 UTCEPSS rescore
  18. 2026-05-27 13:38 UTCEPSS rescore
  19. 2026-05-26 13:41 UTCEPSS rescore
  20. 2026-05-26 13:41 UTCEPSS rescore
  21. 2026-05-25 19:16 UTCOSV refresh
  22. 2026-05-22 21:15 UTCEPSS rescore
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-22 21:15 UTCEPSS rescore
  25. 2026-05-20 22:37 UTCEPSS rescore
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-18 21:29 UTCEPSS rescore
  28. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (2 Metasploit modules) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-24434✓ verified
    First seen Jan 29, 2013

    Ruby on Rails - JSON Processor YAML Deserialization Code Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/http/rails_json_yaml_code_exec✓ verified
    First seen Jan 28, 2013

    Ruby on Rails JSON Processor YAML Deserialization Code Execution

    Open source ↗
  • Metasploitauxiliary/scanner/http/rails_json_yaml_scanner✓ verified
    First seen Jan 1, 2013

    Ruby on Rails JSON Processor YAML Deserialization Scanner

    Open source ↗
  • GitHub PoCheroku/heroku-CVE-2013-0333
    First seen Jan 29, 2013
    Open source ↗

Related CVEs(same product)

Frequently asked(4)

What is CVE-2013-0333?
CVE-2013-0333 is a high vulnerability published on January 30, 2013. lib/active_support/json/backends/yaml.rb in Ruby on Rails 2.3.x before 2.3.16 and 3.0.x before 3.0.20 does not properly convert JSON data to YAML data for processing by a YAML parser, which allows remote attackers to execute arbitrary code, conduct SQL injection attacks, or bypass authentication…
When was CVE-2013-0333 disclosed?
CVE-2013-0333 was first published on January 30, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-0333 actively exploited?
CVE-2013-0333 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 96% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2013-0333?
A fix for CVE-2013-0333 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-0333

Explore →

Is Your Infrastructure Affected by CVE-2013-0333?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs