How severe is CVE-2017-8031?

CVE-2017-8031 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-8031?

CVE-2017-8031 affects the following packages: org.cloudfoundry.identity:cloudfoundry-identity-server (Maven), org.cloudfoundry.identity:cloudfoundry-identity-server (Maven), org.cloudfoundry.identity:cloudfoundry-identity-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-8031?

Update org.cloudfoundry.identity:cloudfoundry-identity-server to 4.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-8031 is resolved across your whole dependency graph.

How do I detect CVE-2017-8031 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.cloudfoundry.identity:cloudfoundry-identity-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2017-8031 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2017-8031?

O3 pinpoints whether CVE-2017-8031 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2017-8031 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-8031 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-8031?

CVE-2017-8031 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2017-8031 published, and has it been updated?

CVE-2017-8031 was published on November 27, 2017 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2017-8031: cloudfoundry-identity-ser… Denial of Service (Me…

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk61th percentile+0.67%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

☕org.cloudfoundry.identity:cloudfoundry-identity-server☕org.cloudfoundry.identity:cloudfoundry-identity-server☕org.cloudfoundry.identity:cloudfoundry-identity-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in Cloud Foundry Foundation cf-release (all versions prior to v279) and UAA (30.x versions prior to 30.6, 45.x versions prior to 45.4, 52.x versions prior to 52.1). In some cases, the UAA allows an authenticated user for a particular client to revoke client tokens for other users on the same client. This occurs only if the client is using opaque tokens or JWT tokens validated using the check_token endpoint. A malicious actor could cause denial of service.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	≥ 4.6.0&&< 4.7.1	4.7.1
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	≥ 4.0.0&&< 4.5.3	4.5.3
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	all versions	3.20.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.cloudfoundry.identity:cloudfoundry-identity-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.cloudfoundry.identity:cloudfoundry-identity-server to 4.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-8031 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2017-8031 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2017-8031. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in Cloud Foundry Foundation cf-release (all versions prior to v279) and UAA (30.x versions prior to 30.6, 45.x versions prior to 45.4, 52.x versions prior to 52.1). In some cases, the UAA allows an authenticated user for a particular client to revoke client tokens for other users on the same client. This occurs only if the client is using opaque tokens or JWT tokens validated using the check_token endpoint. A malicious actor could cause denial of service.

O3 Security · Impact-Aware SCA

Is CVE-2017-8031 in your dependencies?

O3 detects CVE-2017-8031 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVE-2017-8031