How severe is GHSA-3crr-9vmg-864v?

No CVSS score has been assigned to GHSA-3crr-9vmg-864v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3crr-9vmg-864v?

GHSA-3crr-9vmg-864v affects the following packages: activerecord (RubyGems), activerecord (RubyGems), activerecord (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-3crr-9vmg-864v?

Update activerecord to 2.3.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3crr-9vmg-864v is resolved across your whole dependency graph.

How do I detect GHSA-3crr-9vmg-864v 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 GHSA-3crr-9vmg-864v 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 GHSA-3crr-9vmg-864v actively exploited in the wild?

No public exploit code has been indexed for GHSA-3crr-9vmg-864v 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 GHSA-3crr-9vmg-864v?

GHSA-3crr-9vmg-864v has an EPSS (Exploit Prediction Scoring System) score of 3.5%, placing it in the 89th 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 GHSA-3crr-9vmg-864v?

GHSA-3crr-9vmg-864v 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 GHSA-3crr-9vmg-864v published, and has it been updated?

GHSA-3crr-9vmg-864v was published on October 24, 2017 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.

Active Record Improper Input Validation

EPSS Exploitation Probability

via FIRST.org ↗

3.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

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

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`

Affected Products

3 products · 62 configurations

OS

enterprise linuxredhat

1 version

6.0

Application

railsrubyonrails

37 versions

2.3.02.3.12.3.22.3.32.3.42.3.92.3.102.3.112.3.122.3.132.3.142.3.15

Application

ruby on railsrubyonrails

2 versions

2.3.173.1.11

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 GHSA-3crr-9vmg-864v 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
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

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.

O3 Security · Impact-Aware SCA

Is GHSA-3crr-9vmg-864v in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works

Active Record Improper Input ValidationGHSA-3crr-9vmg-864v