Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-23974

MEDIUM · 6.7 CVSS v3.1 Published 2024-08-14
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) ISH software installers 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(R) ISH software installers ship with incorrect default file system permissions that allow authenticated local users to modify installer files or associated components, potentially enabling privilege escalation to higher integrity levels.

MitigationApply vendor-supplied patches or updates for Intel ISH software. If no update is available, manually review and restrict permissions on installer directories and files to remove excessive access for standard 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
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. Verify Intel ISH software is installed
    Check for Intel(R) Integrated Sensor Hub (ISH) components in the system. Look for directories named 'Intel' or 'ISHTP' in Program Files, Program Files (x86), or check Windows Registry under HKLM\SOFTWARE\Intel for ISH-related keys.
    Affected if Intel ISH software is found on the system
  2. Locate Intel ISH installation directory
    Identify the primary installation path for Intel ISH software, typically under C:\Program Files\Intel or C:\Program Files (x86)\Intel. Check for subfolders containing 'ISH', 'ISHTP', or sensor-related components.
    Affected if Installation directory exists and contains ISH-related files or folders
  3. Identify installer files and components
    Enumerate all executable files, DLLs, and configuration files within the Intel ISH installation directory. Focus on files with extensions such as .exe, .dll, .msi, .cab, or .inf.
    Affected if Installer-related files or components are present in the installation directory
  4. Check file system permissions on ISH files
    Use icacls or Get-Acl to inspect permissions on the Intel ISH installation directory and its contents. Specifically examine whether standard authenticated users or the Users group have Write, Modify, or Full Control permissions.
    Affected if Standard authenticated users (non-admin accounts) have Write, Modify, or Full Control permissions on ISH files or directories
  5. Verify write access for non-privileged users
    Attempt to create or modify a test file within the Intel ISH installation directory using a standard user account (or simulate this by checking the effective permissions). Alternatively, review the ACL to confirm the Users group or authenticated users have modification rights.
    Affected if Non-administrator accounts can write or modify files in the ISH installation directory

If Intel ISH software is installed and its installer files or directories are writable by standard authenticated users (not restricted to administrators only), the environment is affected by CVE-2024-23974.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or updates for Intel ISH software. If no update is available, manually review and restrict permissions on installer directories and files to remove excessive access for standard users.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-23974 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