CVE-2024-21945
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 · uneditedIncorrect default permissions in the AMD RyzenTM Master monitoring 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 · moderate confidenceThe AMD Ryzen Master monitoring SDK installation directory has incorrect default permissions that allow unprivileged users to modify files in the directory. An attacker with local access could exploit this to achieve privilege escalation and execute arbitrary code with elevated privileges.
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< 2.13.0.2915CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if AMD Ryzen Master Monitoring SDK is installedOpen Programs and Features (appwiz.cpl) or check the installation directory for the presence of AMD Ryzen Master Monitoring SDK softwareAffected if The software is listed as installed or the SDK directory exists on the system
-
Determine the installed versionRight-click the installed application in Programs and Features and select Properties, or check the version information in the SDK directory. Compare the version number to the affected range: versions prior to 2.13.0.2915Affected if The installed version is lower than 2.13.0.2915
-
Locate the AMD Ryzen Master Monitoring SDK installation directoryCheck common installation paths such as C:\Program Files\AMD\RyzenMasterSDK or C:\Program Files (x86)\AMD\RyzenMasterSDK. The directory may also be found by right-clicking the installed application and selecting Open File LocationAffected if The SDK directory exists at the expected installation path
-
Check write permissions on the installation directoryRight-click the SDK installation folder, select Properties, then go to the Security tab. Examine the permissions for Users or non-administrator groups. Alternatively, use icacls <directory> from an elevated command prompt to view effective permissionsAffected if Users or unprivileged accounts have Write or Full Control permissions on the directory, allowing them to modify, add, or delete files in the SDK folder
The system is affected if the AMD Ryzen Master Monitoring SDK version is below 2.13.0.2915 AND the installation directory grants Write or Full Control permissions to unprivileged users or the Users group.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.13.0.2915
Correct the file system permissions on the AMD Ryzen Master monitoring SDK installation directory to remove excessive access rights, ensuring only authorized users and administrators can write to the directory.
2.13.0.2915 or later
- Uninstall the current version of AMD Ryzen Master Monitoring SDK from the system
- Download AMD Ryzen Master Monitoring SDK version 2.13.0.2915 or later from the official AMD website (www.amd.com)
- Install the downloaded fixed version of the SDK
- Verify the installation completes successfully
- Confirm that the new version is running by checking the installed software version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21945 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21945 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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