CVSS 3.1
7.2 highCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HHigh (7.2) in cisco unified computing system. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExplain CVE-2024-20365 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-20365?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-20365?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-2024-20365 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 | 4.1(2a) |
| cisco:unified_computing_system | 4.1(2b) |
| cisco:unified_computing_system | 4.1(2c) |
| cisco:unified_computing_system | 4.1(3a) |
| cisco:unified_computing_system | 4.1(3b) |
| cisco:unified_computing_system | 4.1(3c) |
| cisco:unified_computing_system | 4.1(3d) |
| cisco:unified_computing_system | 4.1(3e) |
| cisco:unified_computing_system | 4.1(3f) |
| cisco:unified_computing_system | 4.1(3h) |
| cisco:unified_computing_system | 4.1(3i) |
| cisco:unified_computing_system | 4.1(3j) |
| cisco:unified_computing_system | 4.1(3k) |
| cisco:unified_computing_system | 4.1(3l) |
| cisco:unified_computing_system | 4.1(3m) |
| cisco:unified_computing_system | 4.1(4a) |
| cisco:unified_computing_system | 4.2(1c) |
| cisco:unified_computing_system | 4.2(1d) |
| cisco:unified_computing_system | 4.2(1f) |
| cisco:unified_computing_system | 4.2(1i) |
| cisco:unified_computing_system | 4.2(1k) |
| cisco:unified_computing_system | 4.2(1l) |
| cisco:unified_computing_system | 4.2(1m) |
| cisco:unified_computing_system | 4.2(1n) |
| cisco:unified_computing_system | 4.2(2a) |
| cisco:unified_computing_system | 4.2(2c) |
| cisco:unified_computing_system | 4.2(2d) |
| cisco:unified_computing_system | 4.2(2e) |
| cisco:unified_computing_system | 4.2(3b) |
| cisco:unified_computing_system | 4.2(3d) |
| cisco:unified_computing_system | 4.2(3e) |
| cisco:unified_computing_system | 4.2(3g) |
| cisco:unified_computing_system | 4.2(3h) |
| cisco:unified_computing_system | 4.2(3i) |
| cisco:unified_computing_system | 4.2(3j) |
| cisco:unified_computing_system | 4.2(3k) |
| cisco:unified_computing_system | 4.3(2b) |
| cisco:unified_computing_system | 4.3(2c) |
| cisco:unified_computing_system | 4.3(2e) |
| cisco:unified_computing_system | 4.3(3a) |
| cisco:unified_computing_system | 4.3(3c) |
| cisco:unified_computing_system | 4.3(4a) |
| cisco:unified_computing_system | 4.3(4b) |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.