CVE-2013-0333

NONECVSS 0.09.0▲
EchelonGraph scoreLOW confidence

Score elevated to 9.0 because EPSS predicts 92% probability of exploitation within the next 30 days (top 0.3% of all CVEs). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss
Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 99%
CISA-KEV: Not listedEPSS: 99%CVSS: —Exploit: NoneExposed: 0

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 v3
—
EG Score
9.0(low)
EPSS
99.9%
KEV
Not listed

Published

January 30, 2013

Last Modified

April 29, 2026

References (22)

Patch Availability(3)

Vendor / EcosystemFixed in / 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

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
activesupport3.0.0 ... 3.0.9.rc5 (36 versions)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 2× 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-07-05 10:29 UTCOSV refresh
  2. 2026-07-04 06:27 UTCEPSS rescore
  3. 2026-06-16 21:13 UTCOSV refresh
  4. 2026-06-15 17:44 UTCEPSS rescore
  5. 2026-06-13 22:57 UTCEPSS rescore
  6. 2026-06-12 23:08 UTCEPSS rescore
  7. 2026-06-10 13:18 UTCEPSS rescore
  8. 2026-06-06 13:45 UTCEPSS rescore
  9. 2026-06-06 13:45 UTCEPSS rescore
  10. 2026-05-31 22:28 UTCEPSS rescore
  11. 2026-05-31 22:28 UTCEPSS rescore
  12. 2026-05-29 01:09 UTCEG score recompute
  13. 2026-05-29 01:09 UTCVendor advisory
  14. 2026-05-27 13:38 UTCEPSS rescore
  15. 2026-05-27 13:38 UTCEPSS rescore
  16. 2026-05-26 13:41 UTCEPSS rescore
  17. 2026-05-26 13:41 UTCEPSS rescore
  18. 2026-05-25 19:16 UTCOSV refresh
  19. 2026-05-22 21:15 UTCEPSS rescore
  20. 2026-05-22 21:15 UTCEPSS rescore
  21. 2026-05-22 21:15 UTCEPSS rescore
  22. 2026-05-20 22:37 UTCEPSS rescore
  23. 2026-05-20 22:37 UTCEPSS rescore
  24. 2026-05-18 21:29 UTCEPSS rescore
  25. 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 ↗
  • GitHub PoCheroku/heroku-CVE-2013-0333
    First seen Jan 29, 2013
    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 ↗

Frequently asked(4)

What is CVE-2013-0333?
CVE-2013-0333 is a none 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 in the National Vulnerability Database 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. FIRST EPSS estimates a 99.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-0333?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-0333, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs