CVE-2023-29165
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 · uneditedUnquoted search path or element in some Intel(R) Arc(TM) Control software before version 1.73.5335.2 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 · high confidenceIntel Arc Control software before version 1.73.5335.2 contains an unquoted service path vulnerability where the service executable path is not properly quoted, allowing an authenticated local user to place a malicious executable in an intermediate directory in the path to achieve privilege escalation.
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< 31.0.101.4255< 31.0.101.4255CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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.
-
Locate the Intel Arc Control serviceOpen Command Prompt or PowerShell and run 'sc queryex type= service state= all' to list all services, then search for services containing 'Arc' or 'Intel' in the name. Alternatively, check Services.msc for Intel-related services.Affected if An Intel Arc Control or related Intel graphics service is present on the system
-
Inspect the service executable pathRun 'sc qc <service_name>' where <service_name> is the Intel Arc Control service found in the previous step. Check the BINARY_PATH_NAME field.Affected if The BINARY_PATH_NAME field contains a path that is NOT enclosed in quotation marks (e.g., shows C:\Program Files\Intel\... without quotes rather than "C:\Program Files\Intel\...")
-
Check the installed Intel Arc Control versionNavigate to the Intel Arc Control installation directory (typically under Program Files or Program Files (x86)\Intel), locate the main executable (often named something like ArcControl.exe or similar), right-click and select Properties, then check the Details tab for the Product Version.Affected if The installed version is earlier than 1.73.5335.2 (the fixed version) or the graphics driver version is earlier than 31.0.101.4255
-
Verify the intermediate directories in the service pathIf the service path is unquoted, identify each directory in the path (e.g., for C:\Program Files\Intel\Arc Control\service.exe, check if Program Files or Arc Control are writable). Useicacls or PowerShell to check permissions on each directory.Affected if Any intermediate directory in the unquoted service path is writable by the current user, allowing placement of a malicious executable
The system is affected if an Intel Arc Control service exists with an unquoted executable path AND the installed version is earlier than 1.73.5335.2 (or the graphics driver is earlier than version 31.0.101.4255).
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 · scoped31.0.101.4255
Update Intel Arc Control software to version 1.73.5335.2 or later to remediate the unquoted service path vulnerability.
Intel Arc Control software version 1.73.5335.2
- Upgrade Intel(R) Arc(TM) Control software to version 1.73.5335.2 or later
- Verify the installed version by opening Arc Control and navigating to Settings > About
- Confirm the version number displays 1.73.5335.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29165 — 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-29165 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