CVE-2022-43670: Apache Sling App CMS vulnerable to Cross-site Scripting

CVE-2022-43670 · Severity: low · CVSS 3.1 · Published 2022-11-02

Apache Sling App CMS vulnerable to Cross-site Scripting

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

Quick answers

Is CVE-2022-43670 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-43670 being exploited in the wild.
How severe is CVE-2022-43670?
Low severity, with a CVSS score of 3.1, published 2 November 2022.
Which products and versions are affected?
org.apache.sling:org.apache.sling.cms (Maven) ECOSYSTEM:introduced=0,fixed=1.1.2.
Is there a fix for CVE-2022-43670?
Yes. org.apache.sling:org.apache.sling.cms (Maven): upgrade to 1.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-43670?
Check whether you run org.apache.sling:org.apache.sling.cms (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.

How to fix

  • org.apache.sling:org.apache.sling.cms (Maven): upgrade to 1.1.2 or later
    # set org.apache.sling:org.apache.sling.cms to 1.1.2 in your pom.xml or build.gradle

Affected products

  • org.apache.sling:org.apache.sling.cms (Maven) ECOSYSTEM:introduced=0,fixed=1.1.2

Identifiers

  • CVE-2022-43670
  • GHSA-jj93-4jr5-x45h

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