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 Cloud Foundation n/a · VMware Cloud Foundation | affected | 4.x before 4.2 | none available | cve_cna | |
| n/a/VMware Cloud Foundation n/a · VMware Cloud Foundation | affected | 3.x before 3.10.1.2 | none available | cve_cna | |
| n/a/VMware vCenter Server n/a · VMware vCenter Server | affected | 7.x before 7.0 U1c | none available | cve_cna | |
| n/a/VMware vCenter Server n/a · VMware vCenter Server | affected | 6.7 before 6.7 U3l | none available | cve_cna | |
| n/a/VMware vCenter Server n/a · VMware vCenter Server | affected | 6.5 before 6.5 U3n | none available | cve_cna |
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.