dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-25647

MEDIUM · 6.7 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 →
67/100
Remediation priority · Elevated

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 for some Intel(R) Binary Configuration Tool software for Windows before version 3.4.5 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 confidence

Intel Binary Configuration Tool for Windows before version 3.4.5 ships with overly permissive default file or folder permissions that allow authenticated local users to modify executable files or configuration data, potentially leading to privilege escalation by replacing or modifying protected resources.

MitigationUpgrade Intel Binary Configuration Tool to version 3.4.5 or later, or review and restrict file system permissions on the installation directory to follow least-privilege principles.

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

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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 checks

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

  1. Check if Intel Binary Configuration Tool is installed
    Look for the product in Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check common installation paths like C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\
    Affected if The product is found on the system
  2. Determine the installed version
    Right-click the Intel Binary Configuration Tool executable (typically named IntelBCT.exe or similar) in the installation folder, select Properties, and view the File Version or Product Version field
    Affected if The version number is lower than 3.4.5
  3. Verify installation directory permissions
    Right-click the Intel Binary Configuration Tool installation folder, select Properties, go to the Security tab, and examine the permissions for Users or Authenticated Users groups
    Affected if Users or Authenticated Users have Write or Modify permissions to the installation folder containing executable files or configuration files
  4. Check for overly permissive executable permissions
    Navigate to the installation folder, right-click on .exe or .dll files, select Properties > Security, and verify if non-admin users have permission to modify or replace these files
    Affected if Authenticated local users can modify or replace executable files in the installation directory

A user is affected if Intel Binary Configuration Tool is installed with a version before 3.4.5 AND the installation directory or its executables allow authenticated users to modify files (Write/Modify permissions granted to Users or Authenticated Users).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Intel Binary Configuration Tool to version 3.4.5 or later, or review and restrict file system permissions on the installation directory to follow least-privilege principles.

Recommended fix High confidence

Intel Binary Configuration Tool for Windows version 3.4.5

  1. Identify the currently installed version of Intel(R) Binary Configuration Tool on the Windows system
  2. Navigate to the official Intel download page or support site to obtain version 3.4.5
  3. Download the Intel Binary Configuration Tool version 3.4.5 for Windows
  4. Close any instances of the Intel Binary Configuration Tool currently running
  5. Run the installer for version 3.4.5 and complete the installation following standard Intel installation procedures
  6. Verify the installed version is 3.4.5 or later after installation completes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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