Server Debug And Provisioning ToolApplication · Intel

CVE-2024-35201

HIGH · 7.8 CVSS v3.1 Published 2024-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Incorrect default permissions in the Intel(R) SDP Tool for Windows software all versions may allow an authenticated user to 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 confidence

Intel SDP Tool for Windows contains incorrect default file system permissions that allow an authenticated local user to modify executable files or configuration data, enabling local privilege escalation to higher integrity levels.

MitigationApply correct restrictive ACLs to the Intel SDP Tool installation directory and executables, ensuring standard users cannot write to privileged locations; verify the tool functions correctly after permission changes.

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
Server Debug And Provisioning ToolApplication
Affected:all versions

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
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 checks

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

  1. Check if Intel SDP Tool is installed
    Look for the Intel Server Debug And Provisioning Tool in the system. Common installation paths: C:\Program Files\Intel\SDP_Tool or C:\Program Files (x86)\Intel\SDP_Tool. Also check Windows Programs and Features (Add/Remove Programs) for an entry named 'Intel Server Debug And Provisioning Tool' or similar.
    Affected if The tool is present on the system, proceed to permission checks.
  2. Identify the installation directory
    Locate the main executable (typically named SDPTool.exe, intel_sdp.exe, or similar) using 'where /r C:\ SDPTool.exe' or checking Program Files directories. Note the parent folder path.
    Affected if Installation directory is found, proceed to permission checks.
  3. Check write permissions for standard users on the installation directory
    Right-click the installation folder, go to Properties > Security. Verify the permissions for Users orAuthenticated Users group. Alternatively, useicacls.exe: icacls "<installation_path>" | findstr /i "Users"
    Affected if Users orAuthenticated Users have Write or Modify permissions on the installation folder.
  4. Check write permissions on executable files
    Run: icacls "<installation_path>\*.exe" to list permissions. Verify standard users cannot modify .exe files.
    Affected if Standard users have Write or Modify permissions on executable files in the tool directory.
  5. Check write permissions on configuration files
    Run: icacls "<installation_path>" to list all files and their permissions. Check for .xml, .ini, .config, or .json files that may store settings. Run icacls on individual config files: icacls "<path_to_config_file>"
    Affected if Standard users can modify configuration files in the installation directory or subdirectories.

If the Intel SDP Tool is installed and standard users have Write or Modify permissions on the installation directory, executables, or configuration files, the system is vulnerable to local privilege escalation via CVE-2024-35201.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply correct restrictive ACLs to the Intel SDP Tool installation directory and executables, ensuring standard users cannot write to privileged locations; verify the tool functions correctly after permission changes.

Fix this in Server Debug And Provisioning Tool Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35201 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35201 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