dbcve.org
Radeon SoftwareApplication · Amd

CVE-2024-21937

HIGH · 7.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 24.q2 / 24.6.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 the AMD HIP SDK installation directory could allow an attacker to achieve privilege escalation potentially resulting in arbitrary code execution.

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

The AMD HIP SDK installation directory has overly permissive default access control list (ACL) settings that allow standard users to modify executable files and libraries. A local attacker with regular user privileges can replace SDK binaries with malicious code and execute them with elevated privileges, achieving arbitrary code execution.

MitigationReview and restrict permissions on the AMD HIP SDK installation directory to follow the principle of least privilege, ensuring only administrators have write access to executable locations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Radeon SoftwareApplication
Affected:< 24.6.1< 24.7.1< 24.q2
Radeon Software For HipApplication
Affected:< 24.10.16

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Locate the AMD HIP SDK or Radeon Software installation directory
    Check common installation paths such as C:\Program Files\AMD\ROCm\ or C:\Program Files\AMD\Radeon Software\, and verify if either directory exists using File Explorer or the dir command
    Affected if The directory exists and contains SDK binaries and libraries
  2. Identify the installed version of AMD Radeon Software
    Open Programs and Features (appwiz.cpl), find 'AMD Radeon Software' in the list, and note the version number displayed in the Version column
    Affected if The installed version is less than 24.6.1, less than 24.7.1, or less than 24.q2 (for example, 24.5.x, 24.4.x, etc.)
  3. Identify the installed version of AMD Radeon Software for HIP
    Open Programs and Features, find 'AMD Radeon Software For Hip' or similar HIP SDK entry, and note the version number
    Affected if The installed version is less than 24.10.16
  4. Verify ACL permissions on the AMD HIP SDK installation directory
    Right-click the installation directory (e.g., C:\Program Files\AMD\ROCm\), select Properties, go to the Security tab, and examine the permissions for the 'Users' group or standard user accounts
    Affected if The Users group or standard users are listed with Write or Modify permissions, indicating they can modify executable files and libraries in that directory

You are affected if AMD Radeon Software or AMD Radeon Software For HIP is installed at a version below the affected ranges AND standard user accounts have Write or Modify access to the SDK installation directory.

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
Upgrade available Upgrade to 24.q2 / 24.6.1 / 24.7.1 or later
Fixed in 24.q224.6.124.7.1
Interim mitigation

Review and restrict permissions on the AMD HIP SDK installation directory to follow the principle of least privilege, ensuring only administrators have write access to executable locations.

Recommended fix High confidence

Radeon Software 24.6.1/24.7.1/24.q2 or later; Radeon Software For Hip 24.10.16 or later

  1. 1. Uninstall the current version of AMD Radeon Software or AMD HIP SDK from the system.
  2. 2. Download the latest version of AMD Radeon Software (24.6.1, 24.7.1, 24.q2 or later) or AMD HIP SDK (24.10.16 or later) from the official AMD website at www.amd.com.
  3. 3. Verify the integrity of the downloaded installer file before running.
  4. 4. Run the installer with appropriate administrator privileges.
  5. 5. During installation, ensure default permission settings are applied correctly.
  6. 6. After installation, verify that the HIP SDK installation directory has correct permissions (only administrator and SYSTEM accounts should have write access).

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

Fix this in Radeon Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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