CVE-2013-0269: 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 (resourc
Noroxi assessment
Priority: Monitor (action score 34/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 13.9% (FIRST EPSS); higher than 96.5% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: ruby-json (Debian:12) 1.7.3-3; libjson-ruby (Debian:6.0) 1.1.9-1+deb6u1; ruby1.9.1 (Debian:6.0) 1.9.2.0-2+deb6u5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to ruby-json (Debian:12) 1.7.3-3; libjson-ruby (Debian:6.0) 1.1.9-1+deb6u1; ruby1.9.1 (Debian:6.0) 1.9.2.0-2+deb6u5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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."
- Published
- Feb 12, 2013
- Updated
- Jun 16, 2026
- EPSS
- 13.9% · 96th percentile
- CWE
- CWE-20
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 13.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| rubygems | json gem | cpe:2.3:a:rubygems:json_gem |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rubygems json gem1.5.0
- rubygems json gem1.5.1
- rubygems json gem1.5.2
- rubygems json gem1.5.3
- rubygems json gem1.5.4
- rubygems json gem1.6.0
- rubygems json gem1.6.1
- rubygems json gem1.6.2
- rubygems json gem1.6.3
- rubygems json gem1.6.4
- rubygems json gem1.6.5
- rubygems json gem1.6.6
- rubygems json gem1.6.7
- rubygems json gem1.7.0
- rubygems json gem1.7.1
- rubygems json gem1.7.2
- rubygems json gem1.7.3
- rubygems json gem1.7.4
- rubygems json gem1.7.5
- rubygems json gem1.7.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | ruby-json | before 1.7.3-3 | 1.7.3-3 |
| Debian:6.0 | libjson-ruby | before 1.1.9-1+deb6u1 | 1.1.9-1+deb6u1 |
| Debian:6.0 | ruby1.9.1 | before 1.9.2.0-2+deb6u5 | 1.9.2.0-2+deb6u5 |
| Red Hat:openshift:1::el6 | ruby193-ruby | before 0:1.9.3.327-28.el6 | 0:1.9.3.327-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-ruby-debuginfo | before 0:1.9.3.327-28.el6 | 0:1.9.3.327-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-ruby-devel | before 0:1.9.3.327-28.el6 | 0:1.9.3.327-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-ruby-doc | before 0:1.9.3.327-28.el6 | 0:1.9.3.327-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-ruby-irb | before 0:1.9.3.327-28.el6 | 0:1.9.3.327-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-ruby-libs | before 0:1.9.3.327-28.el6 | 0:1.9.3.327-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-ruby-tcltk | before 0:1.9.3.327-28.el6 | 0:1.9.3.327-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-rubygem-bigdecimal | before 0:1.1.0-28.el6 | 0:1.1.0-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-rubygem-io-console | before 0:0.3-28.el6 | 0:0.3-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-rubygem-json | before 0:1.5.4-28.el6 | 0:1.5.4-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-rubygem-minitest | before 0:2.5.1-28.el6 | 0:2.5.1-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-rubygem-rake | before 0:0.9.2.2-28.el6 | 0:0.9.2.2-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-rubygem-rdoc | before 0:3.9.4-28.el6 | 0:3.9.4-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-rubygems | before 0:1.8.23-28.el6 | 0:1.8.23-28.el6 |
| Red Hat:openshift:1::el6 | ruby193-rubygems-devel | before 0:1.8.23-28.el6 | 0:1.8.23-28.el6 |
| Red Hat:openshift:1::el6 | rubygem-json | before 0:1.7.3-2.el6op | 0:1.7.3-2.el6op |
| Red Hat:openshift:1::el6 | rubygem-json-debuginfo | before 0:1.7.3-2.el6op | 0:1.7.3-2.el6op |
| Red Hat:openshift:1::el6 | rubygem-json-doc | before 0:1.7.3-2.el6op | 0:1.7.3-2.el6op |
| Red Hat:openshift:1::el6 | rubygem-rdoc | before 0:3.8-9.el6op | 0:3.8-9.el6op |
| Red Hat:openshift:1::el6 | rubygem-rdoc-doc | before 0:3.8-9.el6op | 0:3.8-9.el6op |
| RubyGems | json | from 1.6.0 · before 1.6.8 | 1.6.8 |
+2
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libjson-ruby | 1.1.9-1+deb6u1 · Debian:6.0 | Package registry (OSV) |
| debian:ruby-json | 1.7.3-3 · Debian:12 | Package registry (OSV) |
| debian:ruby1.9.1 | 1.9.2.0-2+deb6u5 · Debian:6.0 | Package registry (OSV) |
| red hat:ruby193-ruby | 0:1.9.3.327-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-ruby-debuginfo | 0:1.9.3.327-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-ruby-devel | 0:1.9.3.327-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-ruby-doc | 0:1.9.3.327-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-ruby-irb | 0:1.9.3.327-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-ruby-libs | 0:1.9.3.327-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-ruby-tcltk | 0:1.9.3.327-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-rubygem-bigdecimal | 0:1.1.0-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-rubygem-io-console | 0:0.3-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-rubygem-json | 0:1.5.4-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-rubygem-minitest | 0:2.5.1-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| red hat:ruby193-rubygem-rake | 0:0.9.2.2-28.el6 · Red Hat:openshift:1::el6 | Package registry (OSV) |
| RubyGems:json | 1.5.5 | Package registry (OSV) |
| RubyGems:json | 1.6.8 | Package registry (OSV) |
| RubyGems:json | 1.7.7 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:2 | 2013-02-11 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-2 d
- Published
- TodayOct 28, 2026+5006 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0430 · May 31, 2021(RedHat Güvenlik Güncellemeleri Yayınladı)
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.opensuse.org/opensuse-security-announce/2013-04/msg00001.html
- lists.opensuse.org/opensuse-security-announce/2013-04/msg00015.html
- lists.opensuse.org/opensuse-updates/2013-04/msg00034.html
- rhn.redhat.com/errata/RHSA-2013-0686.html
- rhn.redhat.com/errata/RHSA-2013-0701.html
- rhn.redhat.com/errata/RHSA-2013-1028.html
- rhn.redhat.com/errata/RHSA-2013-1147.html
- secunia.com/advisories/52075
- secunia.com/advisories/52774
- secunia.com/advisories/52902
- spreecommerce.com/blog/multiple-security-vulnerabilities-fixed
- weblog.rubyonrails.org/2013/2/11/SEC-ANN-Rails-3-2-12-3-1-11-and-2-3-17-have-been-released/
- www.openwall.com/lists/oss-security/2013/02/11/7
- www.openwall.com/lists/oss-security/2013/02/11/8
- www.osvdb.org/90074
- www.securityfocus.com/bid/57899
- www.slackware.com/security/viewer.php?l=slackware-security&y=2013&m=slackware-security.426862
- www.ubuntu.com/usn/USN-1733-1
- www.zweitag.de/en/blog/ruby-on-rails-vulnerable-to-mass-assignment-and-sql-injection
Vendor advisories and official records. Exploit/PoC links are deliberately left out.