dbcve.org
Sling ApiApplication · Apache

CVE-2022-32549

MEDIUM · 5.3 CVSS v3.1 Published 2022-06-22
Fix available
A fix is available. Upgrade to after 5.4.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Commons Log <= 5.4.0 and Apache Sling API <= 2.25.0 are vulnerable to log injection. The ability to forge logs may allow an attacker to cover tracks by injecting fake logs and potentially corrupt log files.

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 Commons Log <= 5.4.0 and Apache Sling API <= 2.25.0 contain a log injection vulnerability where unsanitized user input can be written to log files. This allows attackers to forge log entries, potentially covering tracks or corrupting log integrity.

MitigationUpgrade Apache Sling Commons Log to version 5.4.1 or higher and Apache Sling API to version 2.26.0 or higher. If immediate patching is not possible, implement input validation to sanitize or reject newline characters and other log injection payloads before logging.

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 ApiApplication
Affected:<= 2.25.0
Sling Commons LogApplication
Affected:<= 5.4.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Identify Apache Sling Commons Log version
    Locate the commons-log jar in your classpath or check your dependency management system (Maven pom.xml, OSGi bundle list, or WAR file lib directory) for org.apache.sling.commons.log and note the installed version
    Affected if The version is 5.4.0 or lower
  2. Identify Apache Sling API version
    Locate the sling-api jar in your classpath or check your dependency management system (Maven pom.xml, OSGi bundle list, or WAR file lib directory) for org.apache.sling.api and note the installed version
    Affected if The version is 2.25.0 or lower
  3. Determine if application logs user input
    Review application source code or search for calls to the Sling Log API (such as Log.info, Log.warn, Log.error) and trace whether external input (request parameters, headers, user agents, path segments, form data) flows into those log statements
    Affected if User-controlled data is passed directly to logging methods without sanitization of newline or carriage return characters

If either Apache Sling Commons Log is version 5.4.0 or lower or Apache Sling API is version 2.25.0 or lower, AND the application logs unsanitized user input, the environment is vulnerable to log injection.

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 a release after 5.4.0
Interim mitigation

Upgrade Apache Sling Commons Log to version 5.4.1 or higher and Apache Sling API to version 2.26.0 or higher. If immediate patching is not possible, implement input validation to sanitize or reject newline characters and other log injection payloads before logging.

Recommended fix Moderate confidence

Sling API 2.26.0+ and Sling Commons Log 5.5.0+

  1. Check the Apache Sling security advisory for CVE-2022-32549 on lists.apache.org for the fixed versions
  2. Identify all dependencies that include org.apache.sling:org.apache.sling.api and org.apache.sling:org.apache.sling.commons.log in your project
  3. Update the dependency management to use Sling API version 2.26.0 or later and Sling Commons Log version 5.5.0 or later
  4. Rebuild and test the application to ensure logging functionality works correctly
  5. Verify that log output properly escapes or encodes newlines and other special characters to prevent injection

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

Fix this in Sling Api Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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