CVE-2016-0732
No exploitation reported by the sources we read.
- Published2017-09-07
- 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
The identity zones feature in Pivotal Cloud Foundry 208 through 229; UAA 2.0.0 through 2.7.3 and 3.0.0; UAA-Release 2 through 4, when configured with multiple identity zones; and Elastic Runtime 1.6.0 through 1.6.13 allows remote authenticated users with privileges in one zone to gain privileges and perform operations on a different zone via unspecified vectors.
Timeline
dates in UTC- 2017-09-0713: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-2016-0732?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-0732?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 |
|---|---|---|---|
| 2.0 | = 2.0.0 | no fix published | NVD |
| 2.0 | = 2.0.1 | no fix published | NVD |
| 2.0 | = 2.0.2 | no fix published | NVD |
| 2.0 | = 2.0.3 | no fix published | NVD |
| 2.1 | = 2.1.0 | no fix published | NVD |
| 2.2 | = 2.2.0 | no fix published | NVD |
| 2.2 | = 2.2.1 | no fix published | NVD |
| 2.2 | = 2.2.2 | no fix published | NVD |
| 2.2 | = 2.2.3 | no fix published | NVD |
| 2.2 | = 2.2.4 | no fix published | NVD |
| 2.2 | = 2.2.4.1 | no fix published | NVD |
| 2.2 | = 2.2.5 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.6 | = 1.6.0 | no fix published | NVD |
| 1.6 | = 1.6.1 | no fix published | NVD |
| 1.6 | = 1.6.2 | no fix published | NVD |
| 1.6 | = 1.6.3 | no fix published | NVD |
| 1.6 | = 1.6.4 | no fix published | NVD |
| 1.6 | = 1.6.5 | no fix published | NVD |
| 1.6 | = 1.6.6 | no fix published | NVD |
| 1.6 | = 1.6.7 | no fix published | NVD |
| 1.6 | = 1.6.8 | no fix published | NVD |
| 1.6 | = 1.6.9 | no fix published | NVD |
| 1.6 | = 1.6.10 | no fix published | NVD |
| 1.6 | = 1.6.11 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.x | = 2 | no fix published | NVD |
| 3.x | = 3 | no fix published | NVD |
| 4.x | = 4 | no fix published | NVD |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- pivotal.ioMitigation · Vendor 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.18.8read 2026-10-23
- NVDCVSS 2.06.5read 2026-10-23
- NVDweakness (CWE)CWE-269read 2026-10-23
- FIRST EPSSEPSS score1.2 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2017-09-07
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-0732?
Is CVE-2016-0732 actively exploited?
What is the CVSS score for CVE-2016-0732?
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.