CVE-2022-32224
CRITICALCVE-2022-32224 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in activerecord. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2022-32224 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Active Record RCE bug with Serialized Columns
Real-World Exposure
activerecord💎activerecord💎activerecord💎activerecordReal-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 possible escalation to RCE vulnerability exists when using YAML serialized columns in Active Record < 7.0.3.1, <6.1.6.1, <6.0.5.1 and <5.2.8.1 which could allow an attacker, that can manipulate data in the database (via means like SQL injection), the ability to escalate to an RCE.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | activerecord | ≥ 7.0.0&&< 7.0.3.1 | 7.0.3.1 |
| 💎RubyGems | activerecord | ≥ 6.1.0&&< 6.1.6.1 | 6.1.6.1 |
| 💎RubyGems | activerecord | ≥ 6.0.0&&< 6.0.5.1 | 6.0.5.1 |
| 💎RubyGems | activerecord | all versions | 5.2.8.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 dependencyDetect
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 7.0.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-32224 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 CVE-2022-32224 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 CVE-2022-32224. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-32224 in your dependencies?
O3 detects CVE-2022-32224 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.