CVE-2017-15717: Cross-site Scripting in Apache Sling XSS Protection API

CVE-2017-15717 · Severity: low · CVSS 3 · Published 2022-05-14

Cross-site Scripting in Apache Sling XSS Protection API

Technologies: org.apache.sling:org.apache.sling.xss (Maven), org.apache.sling:org.apache.sling.xss.compat (Maven). Vendors: Maven.

Quick answers

Is CVE-2017-15717 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-15717 being exploited in the wild.
How severe is CVE-2017-15717?
Low severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?
org.apache.sling:org.apache.sling.xss (Maven) ECOSYSTEM:introduced=1.0.4,fixed=2.0.4.
Is there a fix for CVE-2017-15717?
Yes. org.apache.sling:org.apache.sling.xss (Maven): upgrade to 2.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-15717?
Check whether you run org.apache.sling:org.apache.sling.xss (Maven) or org.apache.sling:org.apache.sling.xss.compat (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.xss (Maven): upgrade to 2.0.4 or later
    # set org.apache.sling:org.apache.sling.xss to 2.0.4 in your pom.xml or build.gradle

Affected products

  • org.apache.sling:org.apache.sling.xss (Maven) ECOSYSTEM:introduced=1.0.4,fixed=2.0.4
  • org.apache.sling:org.apache.sling.xss.compat (Maven)

Identifiers

  • CVE-2017-15717
  • GHSA-7mfw-43c4-45mq

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