User Account and Authentication vulnerabilitiesRanked by how likely they are to be used.
User Account and Authentication is made by Cloudfoundry. We track 9 published vulnerabilities in it, across 276 versions. None of them is on the list of flaws known to be exploited today. If you run User Account and Authentication, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which User Account and Authentication vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of User Account and Authentication's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which User Account and Authentication 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.
- 1.3%CVE-2019-11278High
CF UAA versions prior to 74.1.0, allow external input to be directly queried against.
- 1.3%CVE-2019-11293Medium
Cloud Foundry UAA Release, versions prior to v74.10.0, when set to logging level DEBUG, logs client_secret credentials when sent as a query parameter.
- 1.3%CVE-2019-11290High
Cloud Foundry UAA Release, versions prior to v74.8.0, logs all query parameters to tomcat’s access file.
- 1.0%CVE-2021-22001High
In UAA versions prior to 75.3.0, sensitive information like relaying secret of the provider was revealed in response when deletion request of an identity provider( IdP) of type “oauth 1.0” was sent to UAA server.
- 0.8%CVE-2019-11274Medium
Cloud Foundry UAA, versions prior to 74.0.0, is vulnerable to an XSS attack.
- 0.7%CVE-2021-22098Medium
UAA server versions prior to 75.4.0 are vulnerable to an open redirect vulnerability.
- 0.5%CVE-2020-5402High
In Cloud Foundry UAA, versions prior to 74.14.0, a CSRF vulnerability exists due to the OAuth2 state parameter not being checked in the callback function when authenticating with external identity providers.
- 0.4%CVE-2023-20903Medium
This disclosure regards a vulnerability related to UAA refresh tokens and external identity providers.Assuming that an external identity provider is linked to the UAA, a refresh token is issued to a client on behalf...
Running User Account and Authentication? 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
CF UAA versions prior to 74.1.0, allow external input to be directly queried against. A remote malicious user with 'client.write' and 'groups.update' can craft a SCIM query, which leaks information that allows an escalation of privileges, ultimately allowing the malicious user to gain control of UAA scopes they should not have.
- Matched to
- User Account and Authentication 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 9 published vulnerabilities listed under the name User Account and Authentication, across 276 versions.
None of User Account and Authentication's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track User Account and Authentication. 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.