CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NMedium (5.3) in cisco unified computing system. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExplain CVE-2020-26062 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-26062?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-26062?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-26062 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| cisco:unified_computing_system | 3.2(1d) |
| cisco:unified_computing_system | 3.2(2b) |
| cisco:unified_computing_system | 3.2(2c) |
| cisco:unified_computing_system | 3.2(2d) |
| cisco:unified_computing_system | 3.2(2e) |
| cisco:unified_computing_system | 3.2(2f) |
| cisco:unified_computing_system | 3.2(3a) |
| cisco:unified_computing_system | 3.2(3b) |
| cisco:unified_computing_system | 3.2(3d) |
| cisco:unified_computing_system | 3.2(3e) |
| cisco:unified_computing_system | 3.2(3g) |
| cisco:unified_computing_system | 3.2(3h) |
| cisco:unified_computing_system | 3.2(3i) |
| cisco:unified_computing_system | 3.2(3j) |
| cisco:unified_computing_system | 3.2(3k) |
| cisco:unified_computing_system | 3.2(3l) |
| cisco:unified_computing_system | 3.2(3n) |
| cisco:unified_computing_system | 3.2(3o) |
| cisco:unified_computing_system | 3.2(3p) |
| cisco:unified_computing_system | 4.0(1a) |
| cisco:unified_computing_system | 4.0(1b) |
| cisco:unified_computing_system | 4.0(1c) |
| cisco:unified_computing_system | 4.0(1d) |
| cisco:unified_computing_system | 4.0(2a) |
| cisco:unified_computing_system | 4.0(2b) |
| cisco:unified_computing_system | 4.0(2d) |
| cisco:unified_computing_system | 4.0(2e) |
| cisco:unified_computing_system | 4.0(4a) |
| cisco:unified_computing_system | 4.0(4b) |
| cisco:unified_computing_system | 4.0(4c) |
| cisco:unified_computing_system | 4.0(4d) |
| cisco:unified_computing_system | 4.0(4e) |
| cisco:unified_computing_system | 4.0(4f) |
| cisco:unified_computing_system | 4.0(4g) |
| cisco:unified_computing_system | 4.0(4h) |
| cisco:unified_computing_system | 4.0(4i) |
| cisco:unified_computing_system | 4.1(1a) |
| cisco:unified_computing_system | 4.1(1b) |
| cisco:unified_computing_system | 4.1(1c) |
| cisco:unified_computing_system | 4.1(1d) |
| cisco:unified_computing_system | 4.1(1e) |
| cisco:unified_computing_system | 4.1(2a) |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.