CVE-2023-35769
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 · uneditedUncontrolled search path in some Intel(R) CIP software before version 2.4.10577 may allow an authenticated user to potentially enable escalation of privilege via local access.
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 · moderate confidenceUncontrolled search path vulnerability in Intel CIP software allows an authenticated local user to potentially escalate privileges by placing malicious files in a path where the application searches for libraries or executables before version 2.4.10577.
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< 2.4.10577CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Intel CIP software is installedCheck for Intel Computing Improvement Program in the system's installed programs list. On Windows, this can be done via Control Panel > Programs and Features, or by querying the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or using 'wmic product get name,version'Affected if Intel CIP software is present on the system
-
Identify the installed versionLocate the Intel CIP application and query its version. Check the program's installation directory for version information, or right-click the executable in Task Manager and view Properties for version detailsAffected if Version returned is less than 2.4.10577 (affected versions are < 2.4.10577)
-
Determine if the application runs with elevated privilegesCheck the process properties of Intel CIP to see if it executes with elevated or administrator-level permissions. This can be done via Task Manager > Details tab or by examining the service configuration if Intel CIP runs as a serviceAffected if Intel CIP runs with higher privileges than a standard user, enabling potential privilege escalation
-
Inspect file system permissions on application directoriesExamine write permissions on the Intel CIP installation directory and any directories in its search path. Use 'icacls' or File Explorer properties to check which standard users or groups have write access to these locationsAffected if Untrusted authenticated users can write to directories that Intel CIP searches for libraries or executables
The system is affected if Intel CIP software version is present and is lower than 2.4.10577, and untrusted users have write access to directories in the application's search path.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.4.10577
Upgrade Intel CIP software to version 2.4.10577 or later. Restrict file system permissions to prevent untrusted users from writing to directories in the application's search path.
Intel CIP version 2.4.10577 or later
- 1. Identify the current version of Intel(R) CIP software installed on the system
- 2. Download Intel(R) CIP version 2.4.10577 or later from the official Intel support website
- 3. Close any running instances of the Intel CIP software
- 4. Uninstall the current version of Intel CIP through Windows Control Panel > Programs and Features
- 5. Install the updated Intel CIP version 2.4.10577 or later
- 6. Restart the system if prompted
- 7. Verify the installed version matches or exceeds 2.4.10577
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35769 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-35769 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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