dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-32942

MEDIUM · 6.7 CVSS v3.1 Published 2025-02-12
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) DSA installer for Windows before version 24.2.19.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

The Intel Data Streaming Accelerator (DSA) installer for Windows versions prior to 24.2.19.5 sets incorrect default permissions on installed files or directories during installation. This allows an authenticated local user to potentially modify or take ownership of files they should not have access to, leading to local privilege escalation.

MitigationUpgrade Intel DSA installer to version 24.2.19.5 or later to obtain the corrected permission settings, then re-run the installer on affected systems to apply proper permissions.

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 DSA installer is present
    Search for Intel Data Streaming Accelerator installation directories in Program Files or Program Files (x86), and check Add/Remove Programs or Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' for Intel DSA entries.
    Affected if Intel DSA installer or driver software is found on the system
  2. Determine installed DSA version
    Locate the installed DSA software and check its version property via file properties, or query the installer version from the Windows registry uninstall keys.
    Affected if The installed version is below 24.2.19.5
  3. Identify DSA installation directories
    Examine the directories where Intel DSA components were installed, typically found in Program Files\Intel or under the DSA installation path identified in registry.
    Affected if DSA installation directories exist on the system
  4. Inspect permissions on DSA directories
    Run 'icacls <directory>' on each DSA installation directory to list ACLs, then verify whether Authenticated Users or standard users have excessive modify or full control permissions.
    Affected if Authenticated local users have Modify or Full Control permissions on DSA installation directories they should not normally access
  5. Check for unauthorized ownership capability
    Use 'icacls <directory>' output to determine if non-privileged users can take ownership of files, which would be indicated by granted Write or FullControl permissions to user groups.
    Affected if Standard authenticated users can modify or take ownership of DSA installation files

A system is affected if Intel DSA is installed with a version prior to 24.2.19.5 and the installation directories grant excessive permissions to authenticated local 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 DSA installer to version 24.2.19.5 or later to obtain the corrected permission settings, then re-run the installer on affected systems to apply proper permissions.

Recommended fix High confidence

Intel(R) DSA installer version 24.2.19.5

  1. Identify the currently installed Intel(R) DSA installer version on the Windows system
  2. Download the Intel(R) DSA installer version 24.2.19.5 or later from Intel's official support website
  3. Run the updated installer with appropriate administrative privileges
  4. Verify the installation completed successfully and confirm the new version is applied
  5. Review and correct file system permissions on the Intel DSA installation directory if necessary to ensure restricted default permissions

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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