CVE-2016-6798: XML External Entity Reference in Apache Sling

Quick answers

Is CVE-2016-6798 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-6798 being exploited in the wild.

How severe is CVE-2016-6798?

Low severity, with a CVSS score of 3, published 17 May 2022.

Which products and versions are affected?

org.apache.sling:org.apache.sling.xss (Maven) ECOSYSTEM:introduced=0,fixed=1.0.12; org.apache.sling:org.apache.sling.xss.compat (Maven) ECOSYSTEM:introduced=0,fixed=1.1.0.

Is there a fix for CVE-2016-6798?

Yes. org.apache.sling:org.apache.sling.xss (Maven): upgrade to 1.0.12 or later; org.apache.sling:org.apache.sling.xss.compat (Maven): upgrade to 1.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2016-6798?

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 1.0.12 or later

  # set org.apache.sling:org.apache.sling.xss to 1.0.12 in your pom.xml or build.gradle

• org.apache.sling:org.apache.sling.xss.compat (Maven): upgrade to 1.1.0 or later

  # set org.apache.sling:org.apache.sling.xss.compat to 1.1.0 in your pom.xml or build.gradle

Affected products

• org.apache.sling:org.apache.sling.xss (Maven) ECOSYSTEM:introduced=0,fixed=1.0.12
• org.apache.sling:org.apache.sling.xss.compat (Maven) ECOSYSTEM:introduced=0,fixed=1.1.0

Identifiers

• CVE-2016-6798
• GHSA-7g54-vgp6-jj5w