Active Record RCE bug with Serialized Columns
When serialized columns that use YAML (the default) are deserialized, Rails uses YAML.unsafe_load to convert the YAML data in to Ruby objects. If an attacker can manipulate data in the database (via means like SQL injection), then it may be possible for the attacker to escalate to an RCE. There are no feasible workarounds for this issue, but other coders (such as JSON) are not impacted.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-32224US | critical9.8 | Exploit | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://discuss.rubyonrails.org/t/cve-2022-32224-possible-rce-escalation-bug-with-serialized-columns-in-active-record/81017WEB
- https://github.com/advisories/GHSA-3hhc-qp5v-9p2jADVISORY
- https://github.com/rails/rails/commit/611990f1a6c137c2d56b1ba06b27e5d2434dcd6aWEB
- https://github.com/rails/rails/commits/main/activerecordPACKAGE
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/activerecord/CVE-2022-32224.ymlWEB
- https://groups.google.com/g/rubyonrails-security/c/MmFO3LYQE8UWEB
- https://lists.debian.org/debian-lts-announce/2026/05/msg00022.htmlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-32224ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan