How severe is CVE-2013-1821?

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

Which packages are affected by CVE-2013-1821?

CVE-2013-1821 affects the following packages: org.jruby:jruby (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-1821?

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

How do I detect CVE-2013-1821 in my Maven dependencies?

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

No public exploit code has been indexed for CVE-2013-1821 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-1821?

CVE-2013-1821 has an EPSS (Exploit Prediction Scoring System) score of 6.9%, placing it in the 94th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-1821?

CVE-2013-1821 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-1821 published, and has it been updated?

CVE-2013-1821 was published on May 17, 2022 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-1821 — jruby

CVE-2013-1821 is a Improper Input Validation vulnerability in org.jruby:jruby. A fix is available for org.jruby:jruby — see the affected versions and patch details below.

Ruby vulnerable to denial of service

Published

May 17, 2022

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.jruby:jruby

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

Description

Jruby resolves this bug in version 1.7.3 as noted in https://www.jruby.org/2013/02/21/jruby-1-7-3.html

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jruby:jruby`	all versions	1.7.3`org.jruby:jruby:1.7.3`

Affected Products

1 product · 14 configurations

Application

rubyruby-lang

≤ 1.9.3

6 versions

1.91.9.11.9.21.9.32.02.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jruby:jruby, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jruby:jruby to 1.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1821 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

Product	Fixed in	Advisory
Fuse ESB Enterprise 7.1.0	see advisory	RHSA-2013:1028
Red Hat Enterprise Linux 5	`ruby-0:1.8.5-29.el5_9`	RHSA-2013:0611
Red Hat Enterprise Linux 6	`ruby-0:1.8.7.352-10.el6_4`	RHSA-2013:0612
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 Hardened Images	`ruby3-3-main-3.3.10-23.1.hum1`	RHSA-2026:7305
Red Hat Hardened Images	`ruby3-4-main-3.4.8-31.1.hum1`	RHSA-2026:7307
Red Hat Hardened Images	`ruby4-0-main-4.0.0-33.3.hum1`	RHSA-2026:8838

Frequently Asked Questions

When reading text nodes from an XML document, the REXML parser can be coerced in to allocating extremely large string objects which can consume all of the memory on a machine, causing a denial of service. Jruby resolves this bug in version 1.7.3 as noted in https://www.jruby.org/2013/02/21/jruby-1-7-3.html

O3 Security · Impact-Aware SCA

Is CVE-2013-1821 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works