How severe is CVE-2013-0269?

No CVSS score has been assigned to CVE-2013-0269 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-0269?

CVE-2013-0269 affects the following packages: json (RubyGems), json (RubyGems), json (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-0269?

Update json to 1.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0269 is resolved across your whole dependency graph.

How do I detect CVE-2013-0269 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for json, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-0269 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2013-0269 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-0269 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-0269?

CVE-2013-0269 has an EPSS (Exploit Prediction Scoring System) score of 13.9%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2013-0269?

CVE-2013-0269 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-0269 published, and has it been updated?

CVE-2013-0269 was published on February 13, 2013 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2013-0269: json SQL Injection

EPSS Exploitation Probability

via FIRST.org ↗

13.9%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

💎json💎json💎json

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

The JSON gem before 1.5.5, 1.6.x before 1.6.8, and 1.7.x before 1.7.7 for Ruby allows remote attackers to cause a denial of service (resource consumption) or bypass the mass assignment protection mechanism via a crafted JSON document that triggers the creation of arbitrary Ruby symbols or certain internal objects, as demonstrated by conducting a SQL injection attack against Ruby on Rails, aka "Unsafe Object Creation Vulnerability."

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`json`	all versions	1.5.5`bundle update json --conservative`
💎RubyGems	`json`	≥ 1.6.0&&< 1.6.8	1.6.8`bundle update json --conservative`
💎RubyGems	`json`	≥ 1.7.0&&< 1.7.7	1.7.7`bundle update json --conservative`

Affected Products

1 product · 20 configurations

Application

json gemrubygems

20 versions

1.5.01.5.11.5.21.5.31.5.41.6.01.6.11.6.21.6.31.6.41.6.51.6.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for json, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update json to 1.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0269 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat Satellite tools ship RubyGem Json 1.4.6 which is earlier than affected 1.5.5 version however, this version of RubyGem is not affected to the flaw. We may update RubyGem in a future release.

Product	Fixed in	Advisory
Fuse ESB Enterprise 7.1.0	see advisory	RHSA-2013:1028
Red Hat JBoss Fuse 6.0	see advisory	RHSA-2013:1185
Red Hat JBoss SOA Platform 5.3	see advisory	RHSA-2013:1147
Red Hat Subscription Asset Manager 1.2	`candlepin-0:0.7.24-1.el6_3`	RHSA-2013:0686
RHEL 6 Version of OpenShift Enterprise	`ruby193-ruby-0:1.9.3.327-28.el6`	RHSA-2013:0701

Frequently Asked Questions

The JSON gem before 1.5.5, 1.6.x before 1.6.8, and 1.7.x before 1.7.7 for Ruby allows remote attackers to cause a denial of service (resource consumption) or bypass the mass assignment protection mechanism via a crafted JSON document that triggers the creation of arbitrary Ruby symbols or certain internal objects, as demonstrated by conducting a SQL injection attack against Ruby on Rails, aka "Unsafe Object Creation Vulnerability."

O3 Security · Impact-Aware SCA

Is CVE-2013-0269 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2013-0269 — json