How severe is CVE-2013-0184?

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

Which packages are affected by CVE-2013-0184?

CVE-2013-0184 affects the following packages: rack (RubyGems), rack (RubyGems), rack (RubyGems), rack (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-0184?

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

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

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2013-0184?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-0184 can be triaged on real exposure rather than presence alone.

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

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

CVE-2013-0184 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 83th 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.

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

CVE-2013-0184 was published on March 1, 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.

💎 RubyGems

Not in CISA KEV

CVE-2013-0184 — rack

Fix: rack/rack@1f61549

CVE-2013-0184 is a security vulnerability in rack. A fix is available for rack — see the affected versions and patch details below.

Rack vulnerable to Denial of Service

Also known asGHSA-v882-ccj6-jc48

Published

Mar 1, 2013

Updated

Apr 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

4 pkgs affected

💎rack💎rack💎rack💎rack

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

Unspecified vulnerability in Rack::Auth::AbstractRequest in Rack 1.1.x before 1.1.5, 1.2.x before 1.2.7, 1.3.x before 1.3.9, and 1.4.x before 1.4.4 allows remote attackers to cause a denial of service via unknown vectors related to "symbolized arbitrary strings."

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`rack`	≥ 1.1.0&&< 1.1.5	1.1.5`bundle update rack --conservative`
💎RubyGems	`rack`	≥ 1.2.0&&< 1.2.7	1.2.7`bundle update rack --conservative`
💎RubyGems	`rack`	≥ 1.3.0&&< 1.3.9	1.3.9`bundle update rack --conservative`
💎RubyGems	`rack`	≥ 1.4.0&&< 1.4.4	1.4.4`bundle update rack --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rack, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rack to 1.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0184 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-0184 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-0184. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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
CloudForms for RHEL 6	`rubygem-activesupport-1:3.0.10-10.el6cf`	RHSA-2013:0548
Red Hat Subscription Asset Manager 1.2	`apache-commons-codec-0:1.7-2.el6_3`	RHSA-2013:0544

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-0184 in your dependencies?

O3 Security finds CVE-2013-0184 across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works