Every applicability statement published about this vulnerability, kept as each source wrote it rather than merged into one verdict. Where sources disagree, both positions are shown.
A statement that names no version covers the whole product, which is not the same as your version falling inside a range. Orderings marked best effort come from schemes with no published comparison algorithm; exact ones follow a published specification.
Precedence decides which claim wins when two sources describe the same product over the same version range. It is a property of the source, not of the claim, and changing it re-ranks the data without re-reading a single document.
| Product | Status | Versions | Remediation | Source | |
|---|---|---|---|---|---|
| n/a/VMware vCenter Server and VMware Cloud Foundation n/a · VMware vCenter Server and VMware Cloud Foundation | affected | VMware vCenter Server (7.0 prior to 7.0 U3d, 6.7 prior to 6.7 U3p and 6.5 prior to 6.5 U3r) and VMware Cloud Foundation (4.x and 3.x prior to 3.11) | none available | cve_cna | |
| vmware/cloud_foundation vmware · cloud_foundation | affected | >= 4.0, < 5.0 | none available | cve_adp | |
| vmware/cloud_foundation vmware · cloud_foundation | affected | >= 3.0, < 3.11 | none available | cve_adp | |
| vmware/vcenter_server vmware · vcenter_server | affected | >= 7.0, < 7.0_u3d | none available | cve_adp | |
| vmware/vcenter_server vmware · vcenter_server | affected | >= 6.7, < 6.7_u3p | none available | cve_adp | |
| vmware/vcenter_server vmware · vcenter_server | affected | >= 6.5, < 6.5_u3r | none available | cve_adp |
A claim with no version range is shown as written rather than expanded: a government catalog naming only a vendor and product is a real statement at zero granularity, and inventing bounds for it would put precision in the record that the source never offered.