How severe is CVE-2013-1854?

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

Which packages are affected by CVE-2013-1854?

CVE-2013-1854 affects the following packages: activerecord (RubyGems), activerecord (RubyGems), activerecord (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-1854?

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

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

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

How do I mitigate CVE-2013-1854 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-1854?

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

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

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

CVE-2013-1854 has an EPSS (Exploit Prediction Scoring System) score of 3.4%, placing it in the 88th 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-1854?

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

CVE-2013-1854 was published on March 19, 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-1854 — activerecord

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

Active Record Improper Input Validation

Also known asGHSA-3crr-9vmg-864v

Published

Mar 19, 2013

Updated

Apr 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% 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

3 pkgs affected

💎activerecord💎activerecord💎activerecord

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 Active Record component in Ruby on Rails 2.3.x before 2.3.18, 3.1.x before 3.1.12, and 3.2.x before 3.2.13 processes certain queries by converting hash keys to symbols, which allows remote attackers to cause a denial of service via crafted input to a where method.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`activerecord`	≥ 2.3.0&&< 2.3.18	2.3.18`bundle update activerecord --conservative`
💎RubyGems	`activerecord`	≥ 3.1.0&&< 3.1.12	3.1.12`bundle update activerecord --conservative`
💎RubyGems	`activerecord`	≥ 3.2.0&&< 3.2.13	3.2.13`bundle update activerecord --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activerecord, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update activerecord to 2.3.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1854 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-1854 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-1854. 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
Red Hat Subscription Asset Manager 1.4	`katello-0:1.4.3.28-1.el6sam_splice`	RHSA-2014:1863
RHEL 6 Version of OpenShift Enterprise	`ruby193-rubygem-activerecord-1:3.2.8-6.el6`	RHSA-2013:0699

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-1854 in your dependencies?

O3 Security finds CVE-2013-1854 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