dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-45067

HIGH · 8.2 CVSS v3.1 Published 2025-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High

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) Gaudi(R) software installers before version 1.18 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 · high confidence

Intel Gaudi software installers before version 1.18 set overly permissive default file system permissions on installed files and directories, allowing authenticated local users to modify executable or configuration files that run with elevated privileges, resulting in local privilege escalation.

MitigationUpgrade to Intel Gaudi software version 1.18 or later which contains corrected installer permissions; alternatively, manually review and restrict file permissions on existing installations to remove unnecessary write access for non-privileged users.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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 Gaudi installation location
    Locate the Intel Gaudi software installation directory - common paths include /opt/intel/ or program files under the Intel directory. Use commands like 'find / -name "habana*" -type d 2>/dev/null' or check Windows registry for Intel Gaudi installation paths.
    Affected if The software is found installed on the system.
  2. Determine installed Intel Gaudi version
    Check the version of the installed Intel Gaudi software. Look for version files in the installation directory, or run 'hl-smi' (if available) which may display version information. Compare the version number to 1.18.
    Affected if The installed version is earlier than 1.18 (e.g., 1.17.x, 1.16.x, etc.).
  3. Inspect file permissions on installation directory
    Use 'ls -la' (Linux) or icacls (Windows) on the Intel Gaudi installation directory to list file permissions. Check if authenticated local users have write (w) permissions to directories and files.
    Affected if Non-privileged users have write permissions to the installation directory or subdirectories.
  4. Verify permissions on executable files
    Examine binary executables and scripts in the installation directory. Use 'ls -la' on executables in bin/, libs/, or similar directories to check if they are writable by non-privileged users.
    Affected if Executable files are writable by non-privileged (non-root/admin) users.
  5. Check configuration file permissions
    Inspect configuration files in the installation (commonly in conf/, config/, etc.). Use 'ls -la' or icacls to determine if config files are writable by non-privileged users.
    Affected if Configuration files are writable by non-privileged users.

The system is affected if Intel Gaudi software version earlier than 1.18 is installed and the installation directory or its executables/configurations are writable by non-privileged 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 to Intel Gaudi software version 1.18 or later which contains corrected installer permissions; alternatively, manually review and restrict file permissions on existing installations to remove unnecessary write access for non-privileged users.

Recommended fix Moderate confidence

Intel Gaudi software version 1.18

  1. Obtain Intel Gaudi software version 1.18 or later from the official Intel download center or support website
  2. Download the installer for Intel Gaudi software version 1.18
  3. Run the installer with appropriate privileges following Intel's installation documentation
  4. After installation, verify that the installed version is 1.18 or later using the Intel Gaudi version checking tool or command

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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