dbcve.org
Management Plugin For SccmPlugin / extension · Amd

CVE-2024-21938

HIGH · 7.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 7.0.0.1318 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 Management Plugin for the Microsoft® System Center Configuration Manager (SCCM) 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 Management Plugin for Microsoft SCCM has incorrect default file system permissions on its installation directory, allowing low-privileged users to modify executable files or libraries. This permission misconfiguration enables an attacker to replace legitimate binaries with malicious ones, achieving privilege escalation to execute arbitrary code with elevated privileges.

MitigationCorrect the file system ACLs on the AMD Management Plugin installation directory to restrict write access to privileged users only, ensuring standard users cannot modify executables, libraries, or configuration files in the installation path.

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
Management Plugin For SccmPlugin / extension
Affected:< 7.0.0.1318

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. Find installed version of AMD Management Plugin for SCCM
    Open Programs and Features (appwiz.cpl) or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*AMD Management Plugin*'} | Select-Object DisplayName, DisplayVersion
    Affected if DisplayVersion is less than 7.0.0.1318 or the product is installed with no version shown (implies older unpatched version)
  2. Locate the installation directory
    Check the InstallLocation property from the registry path above, or search for directory containing 'AMDSCCM' or 'AMD Management Plugin' files
    Affected if Installation directory exists and contains AMD plugin executables and DLLs
  3. Check file system permissions on the installation directory
    Right-click the installation folder, go to Properties > Security tab. Click on 'Users' or 'Authenticated Users' group and check the 'Modify' or 'Write' permission. Alternatively, use icacls <directory> from an elevated command prompt
    Affected if Users group or standard users have Write or Modify permissions granted on the installation directory
  4. Verify write access to executable files
    Run: icacls '<installation_directory>\*.exe' or check Permissions for Users group on .exe files in the directory
    Affected if Standard users can write to or replace .exe files in the installation folder
  5. Verify write access to library files
    Run: icacls '<installation_directory>\*.dll' or check Permissions for Users group on .dll files in the directory
    Affected if Standard users can write to or replace .dll files in the installation folder

The environment is affected if the AMD Management Plugin for SCCM version is below 7.0.0.1318 AND standard (non-privileged) users have Write or Modify permissions on the installation directory or its executable/library files.

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 7.0.0.1318 or later
Fixed in 7.0.0.1318
Interim mitigation

Correct the file system ACLs on the AMD Management Plugin installation directory to restrict write access to privileged users only, ensuring standard users cannot modify executables, libraries, or configuration files in the installation path.

Recommended fix Moderate confidence

7.0.0.1318

  1. Navigate to the AMD support website (www.amd.com) and locate the AMD Management Plugin for Microsoft SCCM
  2. Download the latest version of the AMD Management Plugin for SCCM
  3. Verify the version number is 7.0.0.1318 or higher
  4. Backup the current SCCM configuration and any existing plugin data
  5. Uninstall the current version of AMD Management Plugin for SCCM from the system
  6. Install the updated version (7.0.0.1318 or later) with correct default permissions
  7. Verify the installation completed successfully and the plugin is functioning properly
  8. Confirm that the installation directory now has correct permissions (restricted to appropriate administrators and system accounts)

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

Fix this in Management Plugin For Sccm 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-21938 — 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-21938 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