dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-29083

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 in some Intel(R) Distribution for Python software before version 2024.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 · moderate confidence

This is a local privilege escalation vulnerability in Intel Distribution for Python versions before 2024.2 caused by incorrect default file or directory permissions. An authenticated local user can exploit these overly permissive default settings to gain elevated privileges on the system.

MitigationUpgrade to Intel Distribution for Python version 2024.2 or later which contains corrected default permissions. Alternatively, manually review and restrict file/directory permissions 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. Identify Intel Distribution for Python installation
    Check common installation paths: on Windows look in C:\Program Files\Intel\ or C:\Intel\, on Linux/Unix check /opt/intel/ or ~/intel/. Also check PATH for 'idp' or 'intel-python' commands.
    Affected if Intel Distribution for Python is found on the system
  2. Determine installed version
    Run 'idp --version' or 'intel-python --version' from command line. On Windows, check version in Add/Remove Programs or the installation directory's version.info file.
    Affected if Version is found to be lower than 2024.2 (e.g., 2024.1, 2023.x, etc.)
  3. Verify default permissions on installation directory
    On Windows, right-click the Intel Distribution for Python installation folder, select Properties, then Security tab. On Linux/Unix, run 'ls -la /opt/intel/' or the relevant installation path to list permissions.
    Affected if User/Group permissions allow read, write, or execute access to standard users or the 'Users' group beyond what is required for operation
  4. Check Python package and library directory permissions
    Navigate to the Python lib/site-packages directory within the Intel Distribution (e.g., /opt/intel/intelpython3/lib/python3.x/site-packages/). Run 'ls -la' or check folder properties to view permissions.
    Affected if Directories or files within are writable by non-admin users or have overly broad group permissions

The environment is affected if Intel Distribution for Python version 2024.2 or later is NOT installed AND default installation directories have permissions allowing unprivileged users to modify executable files or libraries.

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 to Intel Distribution for Python version 2024.2 or later which contains corrected default permissions. Alternatively, manually review and restrict file/directory permissions to follow least-privilege principles.

Recommended fix Moderate confidence

2024.2

  1. Check the current version of Intel Distribution for Python installed on the system
  2. Download Intel Distribution for Python version 2024.2 or later from the official Intel website or repository
  3. Install the updated version following Intel's standard installation procedures
  4. Verify the new version is correctly installed and the permissions on the installation directory are set correctly

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-2024-29083 — 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-29083 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