cve.bz

CVE-2025-20295 cisco cisco unified computing system (managed): OS Command Injection

6.0 mediumEPSS 0.2%

Medium (6.0) in cisco cisco unified computing system (managed). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability in the CLI of Cisco UCS Manager Software could allow an authenticated, local attacker with administrative privileges to read or create a file or overwrite any file on the file system of the underlying operating system of an affected device, including system files.   This vulnerability is due to insufficient input validation of command arguments supplied by the user. An attacker could exploit this vulnerability by authenticating to a device and submitting crafted input to the affected command. A successful exploit could allow the attacker to read or create a file or overwrite any file on the file system of the underlying operating system of the affected device, including system files. To exploit this vulnerability, the attacker must have valid administrative credentials on the affected device.

Severity

CVSS 3.1

6.0 medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-08-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-20295 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-20295?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-20295?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-2025-20295 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Cisco Unified Computing System (Managed)4.0(1a)
Cisco Unified Computing System (Managed)4.1(1d)
Cisco Unified Computing System (Managed)4.0(4f)
Cisco Unified Computing System (Managed)4.0(4c)
Cisco Unified Computing System (Managed)4.0(2b)
Cisco Unified Computing System (Managed)4.1(2a)
Cisco Unified Computing System (Managed)4.0(4a)
Cisco Unified Computing System (Managed)4.0(4e)
Cisco Unified Computing System (Managed)3.2(3p)
Cisco Unified Computing System (Managed)4.0(4h)
Cisco Unified Computing System (Managed)3.2(3d)
Cisco Unified Computing System (Managed)3.2(3l)
Cisco Unified Computing System (Managed)3.2(3o)
Cisco Unified Computing System (Managed)4.0(2a)
Cisco Unified Computing System (Managed)4.1(1c)
Cisco Unified Computing System (Managed)4.0(1b)
Cisco Unified Computing System (Managed)3.2(3j)
Cisco Unified Computing System (Managed)3.2(2e)
Cisco Unified Computing System (Managed)4.1(1e)
Cisco Unified Computing System (Managed)4.0(4d)
Cisco Unified Computing System (Managed)3.2(1d)
Cisco Unified Computing System (Managed)3.2(3i)
Cisco Unified Computing System (Managed)4.0(4b)
Cisco Unified Computing System (Managed)4.0(2e)
Cisco Unified Computing System (Managed)4.1(1a)
Cisco Unified Computing System (Managed)3.2(3h)
Cisco Unified Computing System (Managed)4.0(4g)
Cisco Unified Computing System (Managed)3.2(2c)
Cisco Unified Computing System (Managed)3.2(3k)
Cisco Unified Computing System (Managed)3.2(3g)
Cisco Unified Computing System (Managed)3.2(2b)
Cisco Unified Computing System (Managed)4.0(1d)
Cisco Unified Computing System (Managed)3.2(3a)
Cisco Unified Computing System (Managed)4.0(1c)
Cisco Unified Computing System (Managed)3.2(3e)
Cisco Unified Computing System (Managed)3.2(2d)
Cisco Unified Computing System (Managed)4.0(4i)
Cisco Unified Computing System (Managed)3.2(2f)
Cisco Unified Computing System (Managed)4.0(2d)
Cisco Unified Computing System (Managed)4.1(1b)
Cisco Unified Computing System (Managed)3.2(3n)
Cisco Unified Computing System (Managed)3.2(3b)
Cisco Unified Computing System (Managed)4.1(2b)
Cisco Unified Computing System (Managed)4.0(4k)
Cisco Unified Computing System (Managed)4.1(3a)
Cisco Unified Computing System (Managed)4.1(3b)
Cisco Unified Computing System (Managed)4.1(2c)
Cisco Unified Computing System (Managed)4.0(4l)
Cisco Unified Computing System (Managed)4.1(4a)
Cisco Unified Computing System (Managed)4.1(3c)
Cisco Unified Computing System (Managed)4.1(3d)
Cisco Unified Computing System (Managed)4.2(1c)
Cisco Unified Computing System (Managed)4.2(1d)
Cisco Unified Computing System (Managed)4.0(4m)
Cisco Unified Computing System (Managed)4.1(3e)
Cisco Unified Computing System (Managed)4.2(1f)
Cisco Unified Computing System (Managed)4.1(3f)
Cisco Unified Computing System (Managed)4.2(1i)
Cisco Unified Computing System (Managed)4.1(3h)
Cisco Unified Computing System (Managed)4.2(1k)
Cisco Unified Computing System (Managed)4.2(1l)
Cisco Unified Computing System (Managed)4.0(4n)
Cisco Unified Computing System (Managed)4.2(1m)
Cisco Unified Computing System (Managed)4.1(3i)
Cisco Unified Computing System (Managed)4.2(2a)
Cisco Unified Computing System (Managed)4.2(1n)
Cisco Unified Computing System (Managed)4.1(3j)
Cisco Unified Computing System (Managed)4.2(2c)
Cisco Unified Computing System (Managed)4.2(2d)
Cisco Unified Computing System (Managed)4.2(3b)
Cisco Unified Computing System (Managed)4.1(3k)
Cisco Unified Computing System (Managed)4.0(4o)
Cisco Unified Computing System (Managed)4.2(2e)
Cisco Unified Computing System (Managed)4.2(3d)
Cisco Unified Computing System (Managed)4.2(3e)
Cisco Unified Computing System (Managed)4.2(3g)
Cisco Unified Computing System (Managed)4.1(3l)
Cisco Unified Computing System (Managed)4.3(2b)
Cisco Unified Computing System (Managed)4.2(3h)
Cisco Unified Computing System (Managed)4.2(3i)
Cisco Unified Computing System (Managed)4.3(2c)
Cisco Unified Computing System (Managed)4.1(3m)
Cisco Unified Computing System (Managed)4.3(2e)
Cisco Unified Computing System (Managed)4.3(3a)
Cisco Unified Computing System (Managed)4.2(3j)
Cisco Unified Computing System (Managed)4.3(3c)
Cisco Unified Computing System (Managed)4.3(4a)
Cisco Unified Computing System (Managed)4.2(3k)
Cisco Unified Computing System (Managed)4.3(4b)
Cisco Unified Computing System (Managed)4.3(4c)
Cisco Unified Computing System (Managed)4.2(3l)
Cisco Unified Computing System (Managed)4.3(4d)
Cisco Unified Computing System (Managed)4.3(2f)
Cisco Unified Computing System (Managed)4.2(3m)
Cisco Unified Computing System (Managed)4.3(5a)
Cisco Unified Computing System (Managed)4.3(4e)
Cisco Unified Computing System (Managed)4.1(3n)
Cisco Unified Computing System (Managed)4.3(4f)
Cisco Unified Computing System (Managed)4.2(3n)
Cisco Unified Computing System (Managed)4.3(5c)
Cisco Unified Computing System (Managed)4.2(3o)
Cisco Unified Computing System (Managed)4.3(5d)
Cisco Unified Computing System (Managed)4.3(6a)
Cisco Unified Computing System (Managed)4.3(6b)
Cisco Unified Computing System (Managed)4.3(5e)

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON