Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
💎 RubyGems

GHSA-q2qw-rmrh-vv42

HIGH

GHSA-q2qw-rmrh-vv42 is a high-severity (CVSS 7.5) CWE-284 vulnerability in activejob. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-q2qw-rmrh-vv42 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Access Control in activejob

Also known asCVE-2018-16476
Published
Dec 5, 2018
Updated
Feb 17, 2024
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
2.6%probability of exploitation in next 30 days
Lower Risk84th percentile0.00%
0.26%1.20%2.15%3.09%0.8%2.6%Feb 26Jun 26Aug 26

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.

Blast Radius

4 pkgs affected
💎activejob💎activejob💎activejob💎activejob

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

A Broken Access Control vulnerability in Active Job versions >= 4.2.0 allows an attacker to craft user input which can cause Active Job to deserialize it using GlobalId and give them access to information that they should not have.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemsactivejob4.2.0&&< 4.2.114.2.11
💎RubyGemsactivejob5.0.0&&< 5.0.7.15.0.7.1
💎RubyGemsactivejob5.1.0&&< 5.1.6.15.1.6.1
💎RubyGemsactivejob5.2.0&&< 5.2.1.15.2.1.1
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activejob. 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.

  2. Fix

    Update activejob to 4.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q2qw-rmrh-vv42 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-q2qw-rmrh-vv42 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-q2qw-rmrh-vv42. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A Broken Access Control vulnerability in Active Job versions >= 4.2.0 allows an attacker to craft user input which can cause Active Job to deserialize it using GlobalId and give them access to information that they should not have.
O3 Security · Impact-Aware SCA

Is GHSA-q2qw-rmrh-vv42 in your dependencies?

O3 detects GHSA-q2qw-rmrh-vv42 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.