First published: Wed Jul 19 2017(Updated: )
In the XSS Protection API module before 1.0.12 in Apache Sling, the encoding done by the XSSAPI.encodeForJSString() method is not restrictive enough and for some input patterns allows script tags to pass through unencoded, leading to potential XSS vulnerabilities.
Credit: secalert@redhat.com secalert@redhat.com
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 | <1.0.12 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-5394 is classified as a high severity vulnerability due to its potential to allow cross-site scripting (XSS) attacks.
To fix CVE-2016-5394, upgrade to Apache Sling XSS Protection API module version 1.0.12 or higher.
The vulnerability in CVE-2016-5394 is caused by insufficient encoding in the XSSAPI.encodeForJSString() method, allowing script tags to pass through.
CVE-2016-5394 affects versions of the Apache Sling XSS Protection API module prior to 1.0.12.
There are no effective workarounds for CVE-2016-5394; upgrading to a patched version is the recommended solution.