dbcve.org
Ryzen Master Utility For Overclocking ControlApplication · Amd

CVE-2024-21946

HIGH · 7.3 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 2.13.1.3097 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 RyzenTM Master Utility 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

AMD Ryzen Master Utility installs with incorrect default file system permissions in its installation directory, allowing unprivileged users to modify executable files. An attacker with local access can replace legitimate binaries with malicious code that executes with elevated (system/Administrator) privileges, achieving arbitrary code execution.

MitigationRemediate by correcting file system permissions on the installation directory to deny write access to non-privileged users; replace the installation with a properly configured version or manually reset permissions following the principle of least privilege.

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
Ryzen Master Utility For Overclocking ControlApplication
Affected:< 2.13.1.3097

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 AMD Ryzen Master Utility is installed
    Check for the presence of AMD Ryzen Master Utility in the system - look in standard installation locations such as Program Files or verify through system inventory tools
    Affected if The utility is found installed on the system
  2. Identify the installation directory
    Locate the directory where AMD Ryzen Master Utility is installed - typically found under the application vendor folder in Program Files
    Affected if The installation directory exists on the system
  3. Check installed version against affected range
    Inspect the installed version of AMD Ryzen Master Utility and compare to the affected threshold: versions prior to 2.13.1.3097 are vulnerable
    Affected if The installed version is lower than 2.13.1.3097
  4. Inspect file system permissions on the installation directory
    Examine ACLs (Access Control Lists) on the installation directory and its executable files - specifically check if non-privileged users or the Users group have Write or Modify permissions
    Affected if Non-privileged standard users have Write or Modify permissions to executable files in the installation directory
  5. Verify executable file integrity
    Review the executable files within the installation directory to confirm they are owned by TrustedInstaller or SYSTEM and not by standard users, and that they are not writable by unprivileged accounts
    Affected if Executable files are writable by unprivileged users or owned by standard user accounts

The environment is affected if AMD Ryzen Master Utility version is below 2.13.1.3097 AND non-privileged users have write access to executable files in the 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 2.13.1.3097 or later
Fixed in 2.13.1.3097
Interim mitigation

Remediate by correcting file system permissions on the installation directory to deny write access to non-privileged users; replace the installation with a properly configured version or manually reset permissions following the principle of least privilege.

Recommended fix High confidence

2.13.1.3097 or later

  1. Navigate to the official AMD website and download the Ryzen Master Utility version 2.13.1.3097 or later
  2. Uninstall the current version of AMD Ryzen Master Utility from the system through Windows Settings > Apps > Apps & features
  3. Restart the computer to ensure all previous processes are terminated
  4. Install the newly downloaded fixed version of Ryzen Master Utility
  5. Verify the installation was successful by checking the installed version in Apps & features

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

Fix this in Ryzen Master Utility For Overclocking Control Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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