Safeguard
Vulnerability Analysis•

CVE-2023-24591: Medium Search Path Flaw in Intel Binary Config Tool

An uncontrolled search path in Intel Binary Configuration Tool before 3.4.4 may allow local privilege escalation. Medium, CVSS 6.7. Update to 3.4.4.

Safeguard Security Team
3 min read

CVE-2023-24591 is a medium severity uncontrolled search path flaw (CVSS 6.7) in Intel Binary Configuration Tool software before version 3.4.4. An authenticated local user could escalate privileges. Update the tool to 3.4.4 or later and read Intel advisory INTEL-SA-00973 for the details.

What's affected

  • Product: Intel Binary Configuration Tool, versions before 3.4.4, per the record.
  • Fixed: version 3.4.4 or later, per the record description.
  • Attack requirements: authenticated user, local access, high attack complexity, user interaction required.
  • Severity: CVSS 3.1 score 6.7 Medium, vector AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H.

We could not load Intel's advisory with our fetch tool, so the version details above come from the record. Open the Intel advisory for the full affected product list and the exact fixed releases.

How to check if you're exposed

Find the tool and read its version. On Windows, look in Apps and Features, or search for the installed package:

Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" | Where-Object DisplayName -like "*Binary Configuration*" | Select-Object DisplayName, DisplayVersion

The tool is often kept as a portable download rather than installed, so also search engineering folders and shared drives for copies. Compare what you find with 3.4.4.

What to do now

  1. Search for copies of Intel Binary Configuration Tool, installed and portable.
  2. Replace any version older than 3.4.4 with the current release from Intel.
  3. Remove old copies from shared drives and build images.
  4. Read INTEL-SA-00973 for further guidance.
  5. Run the tool only from directories that normal users cannot write to.

Why it matters

The weakness is uncontrolled search path element (CWE-427 (Uncontrolled Search Path Element)). The program looks for a file, such as a library, in locations that a lower privileged user can write to. If an attacker places a file there with the expected name, the program loads it and runs it with its own rights.

The risk depends on where the tool runs. On a single user lab machine it is small. On a shared build host or a jump box where several people can write to the program folder, it is larger. The attack complexity is high and user interaction is needed, which holds the score at 6.7. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.

Quick check

What is a search path flaw in plain terms?

A program looks for a file in several places, in order. If one of those places is writable by an attacker, the program can pick up the wrong file.

Do I need to update if nobody else logs in?

The risk is low on a single user machine, but updating is still the simplest way to close the entry.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.