dbcve.org
Cloud Manageability ServiceApplication · Amd

CVE-2024-21939

HIGH · 7.3 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 2.0.0.232 or later.
See remediation →
73/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 the AMD Cloud Manageability Service (ACMS) Software 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 · moderate confidence

AMD Cloud Manageability Service (ACMS) installs with overly permissive default file system permissions in its installation directory, allowing unprivileged users to modify executables or configuration files that execute with elevated privileges. This misconfiguration enables local privilege escalation by replacing legitimate binaries with malicious code that runs under the context of a privileged account.

MitigationCorrect the default permissions on the ACMS installation directory to restrict write access to privileged administrators only, ensuring that standard users cannot modify executables, DLLs, or configuration files.

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
Cloud Manageability ServiceApplication
Affected:< 2.0.0.232

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

CVSS:3.1/AV:L/AC:L/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 if AMD Cloud Manageability Service is installed
    Open Programs and Features (appwiz.cpl) or run 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed software, and look for 'AMD Cloud Manageability Service' in the list
    Affected if ACMS is not present in the installed programs list (not vulnerable if not installed)
  2. Locate the ACMS installation directory
    Check the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for an entry containing 'AMD Cloud Manageability Service' and look at the InstallLocation value, or check C:\Program Files\AMD\ if that directory exists
    Affected if No ACMS installation directory found (not vulnerable)
  3. Check the installed ACMS version
    Right-click the ACMS service in Services (services.msc), go to Properties, and note the 'Path to executable' which may contain version info, or check the version property of the main executable in the installation directory
    Affected if The installed version is lower than 2.0.0.232 (vulnerable version range)
  4. Inspect file permissions on the ACMS installation directory
    Right-click the ACMS installation folder in File Explorer, select Properties, go to the Security tab, and examine the permissions for Users or Standard users group
    Affected if Users or standard non-admin accounts are granted Write or Modify permissions to the directory
  5. Verify unprivileged user access to executables and config files
    Navigate to the ACMS installation directory, right-click any .exe or .config file, check Security permissions, and confirm if Users or standard users have Write permission
    Affected if Non-admin users can write to .exe, .dll, or .config files in the ACMS directory
  6. Confirm ACMS service runs with elevated privileges
    Open Services (services.msc), locate the ACMS service, check the 'Log on as' account in Properties - typically this will be Local System or a domain admin account
    Affected if The service runs as Local System or another privileged account (mandatory for this privilege escalation to work)

You are affected if ACMS is installed with a version below 2.0.0.232 AND non-admin users have Write access to executables/config files in the installation directory AND the service runs under a privileged account.

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

Correct the default permissions on the ACMS installation directory to restrict write access to privileged administrators only, ensuring that standard users cannot modify executables, DLLs, or configuration files.

Recommended fix High confidence

AMD Cloud Manageability Service 2.0.0.232

  1. Identify the currently installed AMD Cloud Manageability Service version
  2. Download AMD Cloud Manageability Service version 2.0.0.232 or later from the official AMD website
  3. Stop the AMD Cloud Manageability Service if it is currently running
  4. Uninstall the current version of AMD Cloud Manageability Service
  5. Install the updated version (2.0.0.232 or higher)
  6. Restart the service and verify it is running correctly

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

Fix this in Cloud Manageability Service Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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