CVE-2022-32549: Log Injection in Apache Sling Commons Log and Apache Sling API

CVE-2022-32549 · Severity: low · CVSS 3.1 · Published 2022-06-23

Log Injection in Apache Sling Commons Log and Apache Sling API

Technologies: org.apache.sling:org.apache.sling.api (Maven). Vendors: Maven.

Quick answers

Is CVE-2022-32549 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-32549 being exploited in the wild.
How severe is CVE-2022-32549?
Low severity, with a CVSS score of 3.1, published 23 June 2022.
Which products and versions are affected?
org.apache.sling:org.apache.sling.api (Maven) ECOSYSTEM:introduced=0,last_affected=2.25.0; org.apache.sling:org.apache.sling.commons.log (Maven) ECOSYSTEM:introduced=0,last_affected=5.4.0.
Is there a fix for CVE-2022-32549?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2022-32549?
Check whether you run org.apache.sling:org.apache.sling.api (Maven) or org.apache.sling:org.apache.sling.commons.log (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • org.apache.sling:org.apache.sling.api (Maven) ECOSYSTEM:introduced=0,last_affected=2.25.0
  • org.apache.sling:org.apache.sling.commons.log (Maven) ECOSYSTEM:introduced=0,last_affected=5.4.0

Identifiers

  • CVE-2022-32549
  • GHSA-qmx3-m648-hr74

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.