Apache Sling EngineWeb server / proxy · Apache
CVE-2022-45064
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 SlingRequestDispatcher doesn't correctly implement the RequestDispatcher API resulting in a generic type of include-based cross-site scripting issues on the Apache Sling level. The vulnerability is exploitable by an attacker that is able to include a resource with specific content-type and control the include path (i.e. writing content). The impact of a successful attack is privilege escalation to administrative power. Please update to Apache Sling Engine >= 2.14.0 and enable the "Check Content-Type overrides" configuration option.
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 SlingRequestDispatcher incorrectly implements the RequestDispatcher API, allowing an include-based cross-site scripting (XSS) vulnerability. An attacker who can include a resource with specific content-type and control the include path (i.e., write content) can achieve privilege escalation to administrative access.
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
Apache Sling EngineWeb server / proxy
< 2.14.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Determine Apache Sling Engine versionLocate the Sling Engine bundle or JAR file in your deployment (typically in the lib or bundles directory) and check its version metadata, or query the OSGi bundle information via the Apache Felix Web Console if availableAffected if The installed version is lower than 2.14.0
-
Identify RequestDispatcher.include usageSearch your application codebase for calls to javax.servlet.RequestDispatcher.include() or org.apache.sling.api.servlets.SlingRequestDispatcher that handle user-controlled input as the include path parameterAffected if Your application uses include() with path parameters that can be influenced by external input
-
Check content-type header handlingExamine your Sling Engine configuration for the 'Check Content-Type overrides' setting (found in the Apache Sling Engine OSGi configuration or org.apache.sling.engine.impl.SlingRequestProcessor properties)Affected if The 'Check Content-Type overrides' option is disabled or not set, allowing arbitrary content-type overrides during include operations
-
Verify include path access controlsReview your application's access control settings and include pathAllowlist configurations to determine if untrusted users can influence which resources get includedAffected if Include paths accept user-supplied values without proper validation or are not restricted to trusted resources only
-
Assess admin endpoint exposureDetermine whether administrative or privileged Sling servlets/resources (such as Felix Web Console, Sling Admin scripts, or custom admin endpoints) are reachable through the include mechanismAffected if Privileged administrative endpoints can be included by low-privilege users through the vulnerable dispatcher
Your environment is affected if Apache Sling Engine version is below 2.14.0 AND your application uses RequestDispatcher.include with user-influenced paths AND the Check Content-Type overrides configuration is not enabled.
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.
dbcve · scoped2.14.0
Update Apache Sling Engine to version 2.14.0 or later and enable the 'Check Content-Type overrides' configuration option to prevent the include-based XSS attack vector.
Apache Sling Engine 2.14.0
- Upgrade Apache Sling Engine to version 2.14.0 or later
- Enable the 'Check Content-Type overrides' configuration option in the Sling Engine settings
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Apache Sling Engine
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45064 — 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-2022-45064 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