dbcve.org
Sling Servlets ResolverApplication · Apache

CVE-2024-23673

HIGH · 7.5 CVSS v3.1 Published 2024-02-06
Fix available
A fix is available. Upgrade to 2.11.0 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
Malicious code execution via path traversal in Apache Software Foundation Apache Sling Servlets Resolver.This issue affects all version of Apache Sling Servlets Resolver before 2.11.0. However, whether a system is vulnerable to this attack depends on the exact configuration of the system. If the system is vulnerable, a user with write access to the repository might be able to trick the Sling Servlet Resolver to load a previously uploaded script.  Users are recommended to upgrade to version 2.11.0, which fixes this issue. It is recommended to upgrade, regardless of whether your system configuration currently allows this attack or not.

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

A path traversal vulnerability in Apache Sling Servlets Resolver allows authenticated users with write access to the repository to potentially load and execute previously uploaded malicious scripts. The vulnerability exists in all versions before 2.11.0 and its exploitability depends on system configuration.

MitigationUpgrade to Apache Sling Servlets Resolver version 2.11.0 or later. Regardless of current configuration, the upgrade is strongly recommended to eliminate the vulnerability.

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 Servlets ResolverApplication
Affected:< 2.11.0

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify Apache Sling Servlets Resolver version
    Check the OSGi bundle version of the 'org.apache.sling.servlets.resolver' bundle through the Apache Felix Web Console (System Information > OSGi > Bundles) or query the bundle using the OSGi console command 'inspect.capability org.apache.sling.bundleresource.name'
    Affected if The installed version is lower than 2.11.0
  2. Verify script resolver path configuration
    Inspect the Servlets Resolver configuration in the Apache Felix Web Console (Configuration > Apache Sling Servlets Resolver) or check the 'org.apache.sling.servlets.resolver' configuration file in the 'sling' directory. Look for properties controlling script search paths and execution permissions.
    Affected if The resolver is configured to load scripts from paths accessible to authenticated users with write access
  3. Confirm authenticated user write access
    Review user permissions in the Apache Sling Repository (Jackrabbit) by checking the ACLs for the /apps or /libs paths where scripts are stored. Use the Repository Explorer or query the /rep:ACL node for user permissions.
    Affected if Authenticated users have write access to script storage locations such as /apps or /libs directories in the repository
  4. Check for uploaded script execution
    Examine the repository for any non-standard scripts in /apps, /libs, or other script search paths configured in the Servlets Resolver. Use the resource browser or repository query to list scripts.
    Affected if Scripts exist in writable locations that the resolver is configured to execute

You are affected if the installed Apache Sling Servlets Resolver version is below 2.11.0 AND the system is configured to allow authenticated users with write access to load scripts from user-writable repository paths.

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 2.11.0 or later
Fixed in 2.11.0
Interim mitigation

Upgrade to Apache Sling Servlets Resolver version 2.11.0 or later. Regardless of current configuration, the upgrade is strongly recommended to eliminate the vulnerability.

Recommended fix High confidence

Apache Sling Servlets Resolver 2.11.0

  1. 1. Identify the current version of Apache Sling Servlets Resolver in your project dependencies
  2. 2. Locate the dependency management file (pom.xml, build.gradle, or similar)
  3. 3. Update the Apache Sling Servlets Resolver dependency version to 2.11.0
  4. 4. Rebuild and test the application to ensure the upgrade doesn't break existing functionality
  5. 5. Deploy the updated application to your environment
Caveat Review release notes for 2.11.0 to check for any breaking changes; minor version upgrade suggests limited compatibility impact

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

Fix this in Sling Servlets Resolver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
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,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23673 — 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-2024-23673 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