dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-31940

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
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) Thread Director Visualizer software before version 1.1.1 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

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 confidence

This is a local privilege escalation vulnerability in Intel Thread Director Visualizer (versions before 1.1.1) caused by incorrect default file/system permissions in Ring 3 user space. An unprivileged authenticated user with local access can exploit this high-complexity flaw to gain elevated privileges on the system.

MitigationUpgrade Intel Thread Director Visualizer to version 1.1.1 or later to obtain the corrected permissions. Audit affected systems for any signs of exploitation given the high impact potential.

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 Thread Director Visualizer is installed
    Look for the product in system program directories or use system inventory tools (e.g., ' Programs and Features' on Windows, rpm/dpkg on Linux, or search for 'Thread Director' in installed programs)
    Affected if The software is found installed on the system
  2. Determine the installed version
    Locate the application executable or check the installed package version (common paths: C:\Program Files\Intel\Thread Director Visualizer or /opt/intel/thread-director-visualizer). Use 'file properties' on Windows or check VERSION.INFO, or run the executable with a version flag if available
    Affected if The version is lower than 1.1.1 (e.g., 1.0.x, 1.0.0)
  3. Inspect file permissions on the installation directory
    Check permissions on the main application folder and subdirectories. On Windows, right-click the folder, go to Properties > Security and verify which users have Write or Full Control. On Linux, run 'ls -la' on the installation path and review owner/group/permissions
    Affected if Unprivileged standard users (non-admin, non-root) have Write, Modify, or Full Control permissions on executable files, configuration files, or service-related binaries within the installation directory
  4. Check for unauthorized modified or new files in the installation directory
    Compare current file listing and timestamps against a known good baseline or inventory. Look for unexpected .exe, .dll, or script files with recent modification dates, or files owned by unprivileged users that should be owned by SYSTEM or root
    Affected if Executable or configuration files have been modified or created by unprivileged accounts, or show ownership by non-admin users where elevated ownership is expected

A system is affected if Intel Thread Director Visualizer version 1.1.0 or earlier is installed AND unprivileged users have write access to application executables or configuration files, indicating the permission flaw exists.

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 Thread Director Visualizer to version 1.1.1 or later to obtain the corrected permissions. Audit affected systems for any signs of exploitation given the high impact potential.

Recommended fix High confidence

Intel Thread Director Visualizer version 1.1.1 or later

  1. Navigate to the official Intel website and locate the Intel Thread Director Visualizer download page
  2. Download the latest version of Intel Thread Director Visualizer (version 1.1.1 or later)
  3. Verify the downloaded file integrity using checksums if provided by Intel
  4. Close any running instances of Intel Thread Director Visualizer
  5. Install the updated version following Intel's installation instructions
  6. Restart the system or the application to ensure the new permissions take effect
  7. Verify the installed version matches the fixed release (1.1.1 or later)

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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