dbcve.org
Sling Jcr BaseApplication · Apache

CVE-2023-25141

HIGH · 7.5 CVSS v3.1 Published 2023-02-14
Fix available
A fix is available. Upgrade to 3.1.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Apache Sling JCR Base < 3.1.12 has a critical injection vulnerability when running on old JDK versions (JDK 1.8.191 or earlier) through utility functions in RepositoryAccessor. The functions getRepository and getRepositoryFromURL allow an application to access data stored in a remote location via JDNI and RMI. Users of Apache Sling JCR Base are recommended to upgrade to Apache Sling JCR Base 3.1.12 or later, or to run on a more recent JDK.

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 confidence

Apache Sling JCR Base before version 3.1.12 contains a JNDI/RMI injection vulnerability in the RepositoryAccessor utility functions (getRepository and getRepositoryFromURL). When the application runs on JDK 1.8.191 or earlier, attackers can exploit these functions to access remote data sources via JNDI and RMI, potentially leading to remote code execution.

MitigationUpgrade Apache Sling JCR Base to version 3.1.12 or later, OR upgrade the JDK to a version newer than 1.8.191.

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 BaseApplication
Affected:>= 2.0.6, < 3.1.12

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Apache Sling JCR Base installation
    Search for the sling-jcr-base JAR file in your application runtime (check lib/, WEB-INF/lib/, classpath, or Maven dependencies). Alternatively, search for the package org.apache.sling.jcr.base in your deployed artifacts.
    Affected if The sling-jcr-base JAR or dependency is found in your environment
  2. Identify the installed version
    Read the JAR filename or inspect the MANIFEST.MF file inside the JAR for the Implementation-Version or Bundle-Version attribute. If using Maven, run 'mvn dependency:tree' and filter for org.apache.sling:sling-jcr-base.
    Affected if The version is 2.0.6 or higher but lower than 3.1.12
  3. Verify JDK version in use
    Run 'java -version' from the command line executing the application, or inspect the JAVA_HOME environment variable. Also check the JDK used by your application server or runtime container.
    Affected if The JDK is version 1.8.191 or earlier (or any JDK 8 update <= 191)
  4. Confirm RepositoryAccessor is invoked
    Search application code for calls to org.apache.sling.jcr.base.internal.RepositoryAccessor.getRepository() or getRepositoryFromURL(String). Also check logs or runtime class loading for these classes.
    Affected if The application code or runtime invokes RepositoryAccessor.getRepository or getRepositoryFromURL methods

Your environment is affected if Apache Sling JCR Base version is between 2.0.6 and 3.1.12 (exclusive), runs on JDK 1.8.191 or earlier, and the application uses RepositoryAccessor.getRepository or getRepositoryFromURL methods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.1.12 or later
Fixed in 3.1.12
Interim mitigation

Upgrade Apache Sling JCR Base to version 3.1.12 or later, OR upgrade the JDK to a version newer than 1.8.191.

Recommended fix High confidence

Apache Sling JCR Base 3.1.12

  1. Identify all applications and dependencies using Apache Sling JCR Base library with version less than 3.1.12
  2. Locate the dependency management file (pom.xml, build.gradle, or similar) that declares the Sling JCR Base dependency
  3. Update the dependency version for 'org.apache.sling:org.apache.sling.jcr.base' from the current version to 3.1.12 or later
  4. Rebuild the application to incorporate the updated dependency
  5. Redeploy the updated application to all affected environments
  6. Test the application to ensure the upgrade does not break existing functionality
Caveat Review Apache Sling release notes for any breaking changes between current and 3.1.12 versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sling Jcr Base Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25141 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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