CyberSecBulletin
CVE-2022-32224NVD status: Modified

https://github.com/rails/rails: Deserialization of Untrusted Data

Published Updated By the CyberSecBulletin desk

CVE-2022-32224 is a critical-severity deserialization of untrusted data vulnerability in https://github.com/rails/rails, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected https://github.com/rails/rails versions: 7.0.3.1, 6.1.6.1, 6.0.5.1, 5.2.8.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.61% chance of exploitation within 30 days, higher than 86% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Activerecord to 5.2.8.1 or 6.0.5.1 or 6.1.6.1 or 7.0.3.1, whichever matches your release line, or a later version.
  2. Read the advisory on github.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Https://github.com/rails/railshttps://github.com/rails/rails7.0.3.1, 6.1.6.1, 6.0.5.1, 5.2.8.1Not stated
Activerecord ProjectActiverecordbefore 5.2.8.1; 6.0.0 up to, but not including, 6.0.5.1; 6.1.0 up to, but not including, 6.1.6.1; 7.0.0 up to, but not including, 7.0.3.15.2.8.1, 6.0.5.1, 6.1.6.1, 7.0.3.1

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.19.8CriticalNVD
CVSS 3.19.8CriticalCISA (ADP)

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

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Deserialization of Untrusted Data

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

How developers prevent this class of flaw

  • If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
  • When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
  • Explicitly define a final object() to prevent deserialization.

More Deserialization of Untrusted Data vulnerabilities (CWE-502)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Advisories

Technical write-ups (may include proof of concept)

Other vulnerabilities in https://github.com/rails/rails

All https://github.com/rails/rails vulnerabilities

Recent Deserialization of Untrusted Data vulnerabilities

Spotted an error? Tell us.