CVE-2017-4973
No exploitation reported by the sources we read.
- Published2017-06-13
- WeaknessCWE-269
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v257; UAA release 2.x versions prior to v2.7.4.14, 3.6.x versions prior to v3.6.8, 3.9.x versions prior to v3.9.10, and other versions prior to v3.15.0; and UAA bosh release (uaa-release) 13.x versions prior to v13.12, 24.x versions prior to v24.7, and other versions prior to v30. A vulnerability has been identified with the groups endpoint in UAA allowing users to elevate their privileges.
Timeline
dates in UTC- 2017-06-1306:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-4973?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-4973?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 30.x | ≤ 30 | no fix published | NVD |
| 13.1 | = 13.1 | no fix published | NVD |
| 13.2 | = 13.2 | no fix published | NVD |
| 13.3 | = 13.3 | no fix published | NVD |
| 13.4 | = 13.4 | no fix published | NVD |
| 13.5 | = 13.5 | no fix published | NVD |
| 13.6 | = 13.6 | no fix published | NVD |
| 13.7 | = 13.7 | no fix published | NVD |
| 13.8 | = 13.8 | no fix published | NVD |
| 13.9 | = 13.9 | no fix published | NVD |
| 13.10 | = 13.10 | no fix published | NVD |
| 13.11 | = 13.11 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.2 | = 2.2.5.4 | no fix published | NVD |
| 2.7 | = 2.7.1 | no fix published | NVD |
| 2.7 | = 2.7.2 | no fix published | NVD |
| 2.7 | = 2.7.3 | no fix published | NVD |
| 2.7 | = 2.7.4 | no fix published | NVD |
| 2.7 | = 2.7.4.1 | no fix published | NVD |
| 2.7 | = 2.7.4.2 | no fix published | NVD |
| 2.7 | = 2.7.4.3 | no fix published | NVD |
| 2.7 | = 2.7.4.4 | no fix published | NVD |
| 2.7 | = 2.7.4.5 | no fix published | NVD |
| 2.7 | = 2.7.4.6 | no fix published | NVD |
| 2.7 | = 2.7.4.7 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 256.x | ≤ 256 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- www.cloudfoundry.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.08.8read 2026-10-23
- NVDCVSS 2.06.5read 2026-10-23
- NVDweakness (CWE)CWE-269read 2026-10-23
- FIRST EPSSEPSS score1.1 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2017-06-13
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-4973?
Is CVE-2017-4973 actively exploited?
What is the CVSS score for CVE-2017-4973?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.