LiveActive security incident?Get immediate response
CVE Record

CVE-2012-5872: ARC (aka ARC2) through 2011-12-01 allows blind SQL Injection in getTriplePatternSQL in ARC2_StoreSelectQuer...

ARC (aka ARC2) through 2011-12-01 allows blind SQL Injection in getTriplePatternSQL in ARC2_StoreSelectQueryHandler.php via comments in a SPARQL WHERE clause.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes a critical SQL injection risk in ARC/ARC2 through 2011-12-01. An exposed application using the vulnerable SPARQL handling path could allow database compromise without authentication. The public bundle does not identify a fixed version or current exploitation.

Executive priority

Treat as urgent if ARC/ARC2 is present on internet-facing or high-trust internal applications. Prioritize asset discovery first because the public record does not provide reliable CPE matching or a named fixed version.

Technical view

ARC/ARC2 getTriplePatternSQL in ARC2_StoreSelectQueryHandler.php allows blind SQL injection through comments in a SPARQL WHERE clause. CVSS 3.1 is 9.8: network reachable, low complexity, unauthenticated, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in applications embedding ARC/ARC2 store query handling, especially public or partner-facing SPARQL endpoints. The affected metadata is incomplete: vendor, product, CPEs, and fixed versions are not provided in the bundle.

Exploitation context

CISA KEV status is false, and the provided sources do not report active exploitation. The vulnerability is still high concern because the CVSS vector indicates remote unauthenticated database-impacting exploitation could be possible where vulnerable ARC/ARC2 code is reachable.

Researcher notes

The key evidence is the CVE description and the referenced advisory naming blind SQL injection in getTriplePatternSQL. Avoid assuming product packaging or exploit activity beyond the bundle. Further work should establish reachable SPARQL input paths and vendor remediation status.

Mitigation direction

  • Inventory applications using ARC or ARC2 through 2011-12-01.
  • Check ARC/ARC2 project guidance for a fixed release or replacement path.
  • Restrict untrusted access to SPARQL endpoints until exposure is resolved.
  • Review database least-privilege controls for affected application accounts.
  • Monitor application and database logs for suspicious query behavior.

Validation and detection

  • Search code and dependency records for ARC2_StoreSelectQueryHandler.php.
  • Confirm whether ARC/ARC2 version is through 2011-12-01.
  • Identify routes accepting SPARQL WHERE clauses from untrusted users.
  • Verify whether vulnerable code is reachable in production deployments.
  • Review logs for unusual SPARQL parsing or database error patterns.
Prepared
Confidence
medium
Sources
3

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.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-5872 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2012-5872Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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