dbcve.org
Computing Improvement ProgramApplication · Intel

CVE-2025-20614

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 2.4.11001 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Intel CIP software before version WIN_DCA_2.4.0.11001 contains a path traversal vulnerability in Ring 3 user applications, allowing an unprivileged attacker to manipulate file paths and achieve privilege escalation when combined with a privileged user session.

MitigationUpdate Intel CIP software to version WIN_DCA_2.4.0.11001 or later. Apply least-privilege principles to limit user access to sensitive directories and monitor for suspicious file operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Computing Improvement ProgramApplication
Affected:< 2.4.11001

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Intel Computing Improvement Program is installed
    Search for Intel CIP software in common installation directories (typically C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\) or use system inventory tools (e.g., run 'Get-WmiObject -Class Win32_Product' or check Add/Remove Programs)
    Affected if Intel CIP software is present on the system
  2. Retrieve the installed version of Intel CIP
    Right-click the Intel CIP executable (commonly named 'IntelComputingImprovementProgram.exe' or similar in the installation folder), select Properties, and view the Details tab for the File Version. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Intel\ or HKLM\SOFTWARE\WOW6432Node\Intel\ for version keys.
    Affected if Unable to determine version or version information is missing
  3. Compare installed version against the affected range
    Compare the retrieved version number to 2.4.11001. Ensure the full version string is evaluated (e.g., 2.4.0.11001 or WIN_DCA_2.4.0.11001 format).
    Affected if Installed version is less than 2.4.11001 (e.g., 2.4.0.10000, 2.3.x.x, etc.)
  4. Verify the vulnerable component is active
    Check if the Intel CIP service or scheduled task is running. Open Services.msc or Task Scheduler and look for Intel Computing Improvement Program entries. Also verify Ring 3 (user-mode) execution context.
    Affected if The Intel CIP service/process is actively running and the vulnerability can be exploited in the current session context

The system is affected by this CVE if Intel Computing Improvement Program is installed with a version number lower than 2.4.11001 and the software or its associated processes are active on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.11001 or later
Fixed in 2.4.11001
Interim mitigation

Update Intel CIP software to version WIN_DCA_2.4.0.11001 or later. Apply least-privilege principles to limit user access to sensitive directories and monitor for suspicious file operations.

Recommended fix Moderate confidence

WIN_DCA_2.4.0.11001 or later

  1. 1. Open the Intel Computing Improvement Program application or Intel Driver & Support Assistant on the affected system
  2. 2. Navigate to the application settings or check for updates
  3. 3. Look for the software update or version information
  4. 4. If an update is available, download and install the version WIN_DCA_2.4.0.11001 or later
  5. 5. Alternatively, visit the official Intel support website and search for the Intel Computing Improvement Program
  6. 6. Download the latest version (WIN_DCA_2.4.0.11001 or newer) from Intel's official download page
  7. 7. Run the installer and follow the on-screen prompts to complete the upgrade
  8. 8. Restart the system after installation to ensure the update takes effect

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Computing Improvement Program Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20614 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data