CVE-2018-11047

UnknownEPSS 1.07%

Last modified

CVE-2018-11047 is a vulnerability of currently unknown severity. Cloud Foundry UAA, versions 4.19 prior to 4.19.2 and 4.12 prior to 4.12.4 and 4.10 prior to 4.10.2 and 4.7 prior to 4.7.6 and 4.5 prior to 4.5.7, incorrectly authorizes requests to admin endpoints by accepting a valid refresh token in lieu of an access token. Refresh tokens by design have a longer expiration time than access tokens, allowing the possessor of a refresh token to authenticate longer than expected. EPSS estimates a 1.07% chance of exploitation in the next 30 days.

Description

Cloud Foundry UAA, versions 4.19 prior to 4.19.2 and 4.12 prior to 4.12.4 and 4.10 prior to 4.10.2 and 4.7 prior to 4.7.6 and 4.5 prior to 4.5.7, incorrectly authorizes requests to admin endpoints by accepting a valid refresh token in lieu of an access token. Refresh tokens by design have a longer expiration time than access tokens, allowing the possessor of a refresh token to authenticate longer than expected. This affects the administrative endpoints of the UAA. i.e. /Users, /Groups, etc. However, if the user has been deleted or had groups removed, or the client was deleted, the refresh token will no longer be valid.

Metrics

EPSS Probability
1.07%

60.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
Pivotal SoftwareCloud Foundry Uaa>= 4.5.0, < 4.5.7
Pivotal SoftwareCloud Foundry Uaa>= 4.7.0, < 4.7.6
Pivotal SoftwareCloud Foundry Uaa>= 4.10.0, < 4.10.2
Pivotal SoftwareCloud Foundry Uaa>= 4.12.0, < 4.12.4
Pivotal SoftwareCloud Foundry Uaa>= 4.19.0, < 4.19.2

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2018-11047?
Cloud Foundry UAA, versions 4.19 prior to 4.19.2 and 4.12 prior to 4.12.4 and 4.10 prior to 4.10.2 and 4.7 prior to 4.7.6 and 4.5 prior to 4.5.7, incorrectly authorizes requests to admin endpoints by accepting a valid refresh token in lieu of an access token. Refresh tokens by design have a longer expiration time than access tokens, allowing the possessor of a refresh token to authenticate longer than expected. This affects the administrative endpoints of the UAA. i.e. /Users, /Groups, etc. However, if the user has been deleted or had groups removed, or the client was deleted, the refresh token will no longer be valid.
How severe is CVE-2018-11047?
Severity scoring for CVE-2018-11047 is pending analysis. The EPSS model estimates a 1.07% probability of exploitation in the next 30 days.
How do I fix CVE-2018-11047?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2018-11047?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST