CVE-2013-0155: n/a vulnerability

CVE-2013-0155: Ruby on Rails 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly consider...

Ruby on Rails 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain "[nil]" values, a related issue to CVE-2012-2660 and CVE-2012-2694.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 14:18 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2013-0155 is a Ruby on Rails query-handling flaw. A remote request could cause an application to apply database filters incorrectly, including unintended NULL checks or missing WHERE clauses. Business impact depends on how the application used affected Rails query patterns, but exposed legacy Rails apps could leak or alter access to records. Exposure is likely limited to legacy Ruby on Rails 3.0, 3.1, or 3.2 applications that accept remote requests and build Active Record queries from request parameters. Prioritize internet-facing legacy Rails applications, especially systems controlling customer, account, or authorization-sensitive records. The flaw is old, but unsupported Rails 3 exposure is a material operational risk. Mitigation focus: Upgrade Rails to 3.0.19, 3.1.10, 3.2.11, or a supported fixed release.; Apply relevant distribution or vendor security updates for packaged Rails deployments.; Review vendor advisories for platform-specific package names and backports..

Prepared: Jun 24, 2026, 12:04 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2013-0155 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jan 13, 2013, 22:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://puppet.com/security/cve/cve-2013-0155CVE reference · x_refsource_CONFIRM
[rubyonrails-security] 20130108 Unsafe Query Generation Risk in Ruby on Rails (CVE-2013-0155)CVE reference · mailing-list, x_refsource_MLIST

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.