Sling XSS Protection API vulnerabilitiesRanked by how likely they are to be used.
Sling XSS Protection API is made by Apache. We track 1 published vulnerability listed under that exact name, across 30 versions. None of them is on the list of flaws known to be exploited today. Apache lists newer releases under their own names, such as Sling XSS Protection API Compat, so check those pages too.
We keep watching the known-exploited list.
Is Sling XSS Protection API listed under other names? Yes.
Apache also lists Sling XSS Protection API under more specific names, such as Sling XSS Protection API Compat. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Sling XSS Protection API vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Sling XSS Protection API's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Sling XSS Protection API flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.9%CVE-2017-15717Medium
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...
Running Sling XSS Protection API? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Sling XSS Protection API on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 1 published vulnerability listed under the name Sling XSS Protection API, across 30 versions.
None of Sling XSS Protection API's vulnerabilities is on the list of flaws known to be exploited today.
Apache also lists Sling XSS Protection API under more specific names, such as Sling XSS Protection API Compat. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Sling XSS Protection API. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.