First published: Wed Jul 19 2017(Updated: )
In the XSS Protection API module before 1.0.12 in Apache Sling, the method XSS.getValidXML() uses an insecure SAX parser to validate the input string, which allows for XXE attacks in all scripts which use this method to validate user input, potentially allowing an attacker to read sensitive data on the filesystem, perform same-site-request-forgery (SSRF), port-scanning behind the firewall or DoS the application.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.sling:org.apache.sling.xss.compat | <1.1.0 | 1.1.0 |
maven/org.apache.sling:org.apache.sling.xss | <1.0.12 | 1.0.12 |
Apache Sling API | <=1.0.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-6798 has a medium severity rating due to its potential to enable XXE attacks.
To fix CVE-2016-6798, upgrade to Apache Sling XSS API version 1.0.12 or later, or the XSS Protection API module version 1.1.0 or later.
CVE-2016-6798 affects Apache Sling versions up to 1.0.10 and the XSS Protection API module before 1.0.12.
CVE-2016-6798 allows for XML External Entity (XXE) attacks, which can lead to exposure of sensitive data.
Yes, CVE-2016-6798 compromises user input validation due to the use of an insecure SAX parser.