CVE-2012-2695: n/a vulnerability

CVE-2012-2695: The Active Record component in Ruby on Rails before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does...

The Active Record component in Ruby on Rails before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does not properly implement the passing of request data to a where method in an ActiveRecord class, which allows remote attackers to conduct certain SQL injection attacks via nested query parameters that leverage improper handling of nested hashes, a related issue to CVE-2012-2661.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 19:42 UTC (UTC+00:00)

Security readout for executives and security teams

Older Ruby on Rails applications may let attackers manipulate database queries through specially structured request parameters. This is a SQL injection class issue in Active Record. Business impact depends on the application’s data and permissions, but affected internet-facing Rails apps should be treated as urgent legacy risk. Exposure is likely limited to legacy Rails 3.0, 3.1, and 3.2 applications or vendor packages that still include vulnerable Rails versions. Internet-facing applications that pass request-derived data into ActiveRecord query construction are the main concern. Prioritize remediation for any exposed Rails 3 application handling sensitive data. The vulnerability is old but serious, and affected systems are likely unsupported legacy assets with broader maintenance risk. Mitigation focus: Upgrade Rails to 3.0.14, 3.1.6, 3.2.6, or a later supported release.; Apply the relevant Red Hat, SUSE, or openSUSE security updates if using packaged Rails.; Retire unsupported Rails 3 applications where upgrade paths are no longer maintainable..

Prepared: Jun 24, 2026, 12:34 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-2012-2695 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: Jun 22, 2012, 14: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

2Source 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
[rubyonrails-security] 20120612 Ruby on Rails SQL Injection (CVE-2012-2695)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.