Skip to content
Fencer Intel
critical 10.0

CVE-2013-0277 in the critical feed json

Active Record contains deserialization of arbitrary YAML

published 13y ago modified 4mo ago also GHSA-fhj9-cjjh-27vm , EUVD-2017-0230

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.5%
EPSS 7.5% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

ActiveRecord in Ruby on Rails before 2.3.17 and 3.x before 3.1.0 allows remote attackers to cause a denial of service or execute arbitrary code via crafted serialized attributes that cause the +serialize+ helper to deserialize arbitrary YAML.

Patch / fix

  • rubygems activerecord 2.3.17, 3.1.0
  • rails Debian 14, Debian 13, Debian 12 2.3.14.1

debian advisories DEBIAN-CVE-2013-0277

Is CVE-2013-0277 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-0277 updated cvss 7.5

rubygem-activerecord: Serialized Attributes YAML Vulnerability with Rails 2.3 and 3.0

  • Red Hat OpenShift Enterprise 1 rubygem-activesupport Red Hat Subscription Asset Manager rubygem-activesupport
    affected: no fix available
  • Red Hat OpenShift Enterprise 1 ruby193-rubygem-activesupport
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

7.50% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected packages

ecosystem package affected fixed in
rubygems activerecord
<2.3.17
>=3.0.0, <3.1.0
2.3.17
3.1.0

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.