How severe is GHSA-9rf5-jm6f-2fmm?

No CVSS score has been assigned to GHSA-9rf5-jm6f-2fmm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9rf5-jm6f-2fmm?

GHSA-9rf5-jm6f-2fmm affects the following packages: activerecord (RubyGems), activerecord (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-9rf5-jm6f-2fmm?

Update activerecord to 4.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9rf5-jm6f-2fmm is resolved across your whole dependency graph.

How do I detect GHSA-9rf5-jm6f-2fmm in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activerecord. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-9rf5-jm6f-2fmm 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 GHSA-9rf5-jm6f-2fmm?

O3 pinpoints whether GHSA-9rf5-jm6f-2fmm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9rf5-jm6f-2fmm actively exploited in the wild?

No public exploit code has been indexed for GHSA-9rf5-jm6f-2fmm 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 type of vulnerability is GHSA-9rf5-jm6f-2fmm?

GHSA-9rf5-jm6f-2fmm is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9rf5-jm6f-2fmm published, and has it been updated?

GHSA-9rf5-jm6f-2fmm 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.

💎 RubyGems

GHSA-9rf5-jm6f-2fmm

GHSA-9rf5-jm6f-2fmm is a CWE-264 vulnerability in activerecord. O3 Security confirms whether GHSA-9rf5-jm6f-2fmm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Active Record subject to strong parameters protection bypass

Also known asCVE-2014-3514

Published

Oct 24, 2017

Updated

Nov 29, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

💎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

activerecord/lib/active_record/relation/query_methods.rb in Active Record in Ruby on Rails 4.0.x before 4.0.9 and 4.1.x before 4.1.5 allows remote attackers to bypass the strong parameters protection mechanism via crafted input to an application that makes create_with calls.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`activerecord`	≥ 4.0.0&&< 4.0.9	4.0.9
💎RubyGems	`activerecord`	≥ 4.1.0&&< 4.1.5	4.1.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activerecord. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update activerecord to 4.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9rf5-jm6f-2fmm 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 pinpoints whether GHSA-9rf5-jm6f-2fmm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9rf5-jm6f-2fmm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`activerecord/lib/active_record/relation/query_methods.rb` in Active Record in Ruby on Rails 4.0.x before 4.0.9 and 4.1.x before 4.1.5 allows remote attackers to bypass the strong parameters protection mechanism via crafted input to an application that makes `create_with` calls.

O3 Security · Impact-Aware SCA

Is GHSA-9rf5-jm6f-2fmm in your dependencies?

O3 detects GHSA-9rf5-jm6f-2fmm across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works