First published: Wed Jan 10 2018(Updated: )
A flaw in the way URLs are escaped and encoded in the org.apache.sling.xss.impl.XSSAPIImpl#getValidHref and org.apache.sling.xss.impl.XSSFilterImpl#isValidHref allows special crafted URLs to pass as valid, although they carry XSS payloads. The affected versions are Apache Sling XSS Protection API 1.0.4 to 1.0.18, Apache Sling XSS Protection API Compat 1.1.0 and Apache Sling XSS Protection API 2.0.0.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Sling XSS Protection API | >1.0.4<=1.0.18 | |
Apache Sling XSS Protection API | =2.0.0 | |
Apache Sling XSS Protection API Compat | =1.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-15717 is classified as a medium severity vulnerability due to its potential to allow XSS attacks.
CVE-2017-15717 affects Apache Sling XSS Protection API versions from 1.0.4 to 1.0.18 and 2.0.0.
To fix CVE-2017-15717, upgrade to a patched version of Apache Sling XSS Protection API above 1.0.18 or a later stable version.
CVE-2017-15717 allows specially crafted URLs to pass validation, potentially allowing for Cross-Site Scripting (XSS) attacks.
Yes, CVE-2017-15717 can be exploited remotely if a user interacts with the maliciously crafted URLs.