How severe is CVE-2012-3353?

CVE-2012-3353 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2012-3353?

CVE-2012-3353 affects the following packages: org.apache.sling:org.apache.sling.jcr.contentloader (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-3353?

Update org.apache.sling:org.apache.sling.jcr.contentloader to 2.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-3353 is resolved across your whole dependency graph.

How do I detect CVE-2012-3353 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.sling:org.apache.sling.jcr.contentloader, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-3353 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2012-3353 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-3353 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-3353?

CVE-2012-3353 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-3353?

CVE-2012-3353 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-3353 published, and has it been updated?

CVE-2012-3353 was published on May 14, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2012-3353 — org.apache.sling.jcr.cont…

HIGH

CVE-2012-3353 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.sling:org.apache.sling.jcr.contentloader. A fix is available for org.apache.sling:org.apache.sling.jcr.contentloader — see the affected versions and patch details below.

Apache Sling JCR ContentLoader XmlReader Arbitrary File Load

Published

May 14, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.apache.sling:org.apache.sling.jcr.contentloader

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The Apache Sling JCR ContentLoader 2.1.4 XmlReader used in the Sling JCR content loader module makes it possible to import arbitrary files in the content repository, including local files, causing potential information leaks. Users should upgrade to version 2.1.6 of the JCR ContentLoader

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.sling:org.apache.sling.jcr.contentloader`	all versions	2.1.6`org.apache.sling:org.apache.sling.jcr.contentloader:2.1.6`

Affected Products

1 product · 1 configurations

Application

sling jcr contentloaderapache

1 version

2.1.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.sling:org.apache.sling.jcr.contentloader, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.sling:org.apache.sling.jcr.contentloader to 2.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-3353 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-3353 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 14, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2012-3353

References

Advisorynvd.nist.gov · CVE 2012 3353 Webissues.apache.org · SLING 2512 Weblists.apache.org · owd2xw86l19dh1f1zlhq41l7wlnd16sk

Related vulnerabilities

This CVE is high severity; 2 of 8 other CVEs with CWE-200 are rated as high or higher (top: high).

CVE-2026-123372CVE-2026-123796CVE-2026-55098GHSA-m3qr-fvp4-78xjCVE-2026-119199CVE-2026-118759CVE-2026-62264GHSA-473q-m89c-ghf8Browse all CWE-200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2012-3353 — org.apache.sling.jcr.cont…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2012-3353 in your dependencies?