Spring Security Oauth vulnerabilitiesRanked by how likely they are to be used.
Spring Security Oauth is made by Pivotal. We track 2 published vulnerabilities in it, across 17 versions. None of them is on the list of flaws known to be exploited today. If you run Spring Security Oauth, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Spring Security Oauth vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Spring Security Oauth's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Spring Security Oauth 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.
- 79%CVE-2016-4977High
When processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to 1.0.5, the response_type parameter value was executed as Spring SpEL which enabled a malicious...
- 1.3%CVE-2022-22969Medium
<Issue Description> Spring Security OAuth versions 2.5.x prior to 2.5.2 and older unsupported versions are susceptible to a Denial-of-Service (DoS) attack via the initiation of the Authorization Request in an OAuth...
Running Spring Security Oauth? 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
When processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to 1.0.5, the response_type parameter value was executed as Spring SpEL which enabled a malicious user to trigger remote code execution via the crafting of the value for response_type.
- Matched to
- Spring Security Oauth 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 2 published vulnerabilities listed under the name Spring Security Oauth, across 17 versions.
None of Spring Security Oauth's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Spring Security Oauth. 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.