Sling Jcr ContentloaderApplication · Apache
CVE-2012-3353
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe XmlReader in Apache Sling JCR ContentLoader version 2.1.4 allows importing arbitrary files from the local filesystem into the JCR content repository, enabling attackers to read sensitive local files and potentially exfiltrate their contents through the content loader functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Sling Jcr ContentloaderApplication
= 2.1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Apache Sling JCR ContentLoader is installedLocate the JCR ContentLoader bundle in the Sling installation: check the OSGi console bundle list, or search for files named 'org.apache.sling.jcr.contentloader-*' in the bundles or lib directoryAffected if The bundle is present in the Sling instance
-
Determine the installed version of JCR ContentLoaderCheck the bundle version: in OSGi console view the bundle details, or inspect the MANIFEST.MF file inside the JAR for Bundle-Version, or use the Sling Web Console to view component metadataAffected if Version is exactly 2.1.4
-
Verify the content loader import endpoint is accessibleCheck if the content loader servlet is registered: look for /system/console/components or /system/console/bundles in the Sling Web Console, and verify the org.apache.sling.jcr.contentloader package is activeAffected if The content loader servlet is active and accessible via HTTP
-
Check for recent content imports from the JCRQuery the JCR repository for recently created content nodes under /libs or /apps that may have been imported via the content loader, or review access logs for POST requests to import endpointsAffected if Unexpected content nodes exist or suspicious import requests appear in logs
You are affected if Apache Sling JCR ContentLoader version 2.1.4 is installed and the content loader functionality is accessible, allowing arbitrary file reads from the local filesystem.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the JCR ContentLoader module from version 2.1.4 to version 2.1.6 or later, as the upgrade addresses the arbitrary file import vulnerability that allows local file inclusion and information disclosure.
Fix this in Sling Jcr Contentloader
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3353 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3353 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data