What is CVE-2013-0269?

CVE-2013-0269 is a high-severity improper input validation vulnerability in json (rubygems), affecting versions < 1.5.5. It is fixed in 1.5.5, 1.6.8, 1.7.7. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

Which versions of json are affected by CVE-2013-0269?

json (rubygems) versions < 1.5.5 is affected.

Is there a fix for CVE-2013-0269?

Yes. CVE-2013-0269 is fixed in 1.5.5, 1.6.8, 1.7.7. Upgrade to this version or later.

Is CVE-2013-0269 exploitable, and should I be worried?

Whether CVE-2013-0269 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2013-0269 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2013-0269 in json

Q: Which versions of json are affected by CVE-2013-0269?

json (rubygems) versions < 1.5.5 is affected.

Q: Is there a fix for CVE-2013-0269?

Yes. CVE-2013-0269 is fixed in 1.5.5, 1.6.8, 1.7.7. Upgrade to this version or later.

Q: Is CVE-2013-0269 exploitable, and should I be worried?

Whether CVE-2013-0269 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2013-0269 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2013-0269?

Upgrade: json to 1.5.5 or later, json to 1.6.8 or later, json to 1.7.7 or later.

Summary

JSON gem has Improper Input Validation vulnerability

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."

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

Affected versions

json (< 1.5.5) json (>= 1.6.0, < 1.6.8) json (>= 1.7.0, < 1.7.7)

Security releases

json → 1.5.5 (rubygems) json → 1.6.8 (rubygems) json → 1.7.7 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

json to 1.5.5 or later; json to 1.6.8 or later; json to 1.7.7 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2013-0269? CVE-2013-0269 is a high-severity improper input validation vulnerability in json (rubygems), affecting versions < 1.5.5. It is fixed in 1.5.5, 1.6.8, 1.7.7. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
Which versions of json are affected by CVE-2013-0269? json (rubygems) versions < 1.5.5 is affected.
Is there a fix for CVE-2013-0269? Yes. CVE-2013-0269 is fixed in 1.5.5, 1.6.8, 1.7.7. Upgrade to this version or later.
Is CVE-2013-0269 exploitable, and should I be worried? Whether CVE-2013-0269 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2013-0269 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2013-0269?
- Upgrade json to 1.5.5 or later
- Upgrade json to 1.6.8 or later
- Upgrade json to 1.7.7 or later

Other vulnerabilities in json

CVE-IDSeverityPackage summary

CVE-2026-33210Highjson: Ruby JSON has a format string injection vulnerability CVE-2025-27788Highjson: Out-of-bounds Read in Ruby JSON Parser CVE-2020-7712Highjson: trentm/json vulnerable to command injection CVE-2020-10663Highjson: Unsafe object creation in json RubyGem