CVE Tools

CVE-2013-0277

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 +ser...

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, GitHub

What to do

The vendor has published a fix. Version details are below where the sources state them.

What it is

From the CVE record

Active Record contains deserialization of arbitrary YAML

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS94th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

7.5% chance of exploitation activity in the next 30 days, which ranks it in the 94th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

A public exploit existed 53 days before the patch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Public exploit / PoCsource: github-poc
  4. Publishedweakness classified

Affected products

And 1 more affected product. See all after sign-in

Technical detail

AV:N/AC:L/Au:N/C:C/I:C/A:C

Scored 10.0 by NVD.

How it is reached

  • Access Vector NetworkExploitable remotely over the network
  • Access Complexity LowNo special conditions required
  • Authentication NoneNo authentication required

Impact if exploited

  • Confidentiality CompleteAll information is disclosed
  • Integrity CompleteAll data can be modified
  • Availability CompleteTotal shutdown of the affected resource

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Rails, not every advisory. This one: public exploit.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store