Cyber Resilience

CVE-2025-20614

Path Traversal in Intel Computing Improvement Program ≤ 2.4.11001

Published
11 November 2025
Modified
26 November 2025
Patch / advisory
CVSS Score v4 5.6
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0014 4th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-20614 is a medium-severity External Control of File Name or Path (CWE-73) vulnerability in Intel Computing Improvement Program. Its CVSS base score is 5.6 (Medium).

Operationally, ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

External control of file name or path for some Intel(R) CIP software before version WIN_DCA_2.4.0.11001 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with a privileged user combined with a low complexity attack may…

more

enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (low) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-20050Same product: Intel Computing Improvement Program
CVE-2025-24838Same product: Intel Computing Improvement Program
CVE-2023-43489Same product: Intel Computing Improvement Program
CVE-2025-24862Same product: Intel Computing Improvement Program
CVE-2025-24307Same product: Intel Computing Improvement Program
CVE-2023-35769Same product: Intel Computing Improvement Program
CVE-2025-24863Same product: Intel Computing Improvement Program
CVE-2024-36482Same product: Intel Computing Improvement Program
CVE-2025-24848Same product: Intel Computing Improvement Program
CVE-2025-24847Same product: Intel Computing Improvement Program

Affected Assets

intel
computing improvement program
≤ 2.4.11001

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation of file/path inputs to block externally supplied names that enable the CWE-73 escalation.

prevent

Enforces access-control decisions on file operations so that Ring-3 manipulation cannot obtain elevated privileges.

prevent

Limits privileges of the Intel CIP process and calling user, reducing the impact of any successful path-based escalation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure SDLC practices include input validation and path sanitization that eliminate this weakness.

PR.AA-05 mostly match
prevents

Least-privilege file authorization directly limits damage from externally controlled paths.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect path-traversal issues but does not itself implement preventive controls.

prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent external file/path manipulation.

prevents

Application security requirements explicitly call for controls against untrusted input influencing file operations.

prevents

Secure architecture principles discourage unsafe path construction but do not prescribe concrete file-name controls.

prevents

Secure coding standards require canonicalization, allow-listing, and bounds checks on file paths, directly eliminating CWE-73.

mitigates

Information access restriction limits which files can be reached, indirectly reducing impact of path manipulation.

References