CVE-2024-21958
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 Provisioning Console 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 Provisioning Console installer sets overly permissive default permissions on its installation directory, allowing unprivileged users to modify executable files or place malicious code. An attacker with local access could escalate privileges by replacing or modifying files in the installation directory to achieve arbitrary code execution 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< 4.0.0.408CVSS 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.
-
Find AMD Provisioning Console installationCheck registry key HKEY_LOCAL_MACHINE\SOFTWARE\AMD\ProvisioningConsole for InstallPath value, or look in common locations: C:\Program Files\AMD\ProvisioningConsoleAffected if The product is not installed or the registry key does not exist means not affected
-
Determine installed versionCheck the version of AmdProvisioningConsole.exe in the installation directory by right-clicking the file, selecting Properties, and viewing the Details tab, or run: (Get-Item 'C:\Program Files\AMD\ProvisioningConsole\AmdProvisioningConsole.exe').VersionInfo.FileVersionAffected if Version is lower than 4.0.0.408 - if version cannot be determined or is not present, verify against the vendor's version listing
-
Identify the installation directory permissionsRight-click the installation folder (e.g., C:\Program Files\AMD\ProvisioningConsole), select Properties > Security tab, and click Advanced. Check the Permission entries for Users or authenticated users group.Affected if Users or authenticated users have Write or Modify permissions, or any non-admin group shows Allow for Create Files/Write Data permission
User is affected if AMD Provisioning Console version is below 4.0.0.408 AND non-privileged users have write/modify access to the installation directory where they could replace executable files.
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 · scoped4.0.0.408
Apply restrictive NTFS permissions to the AMD Provisioning Console installation directory, removing write access for non-admin users and ensuring only authorized administrators can modify executable files.
4.0.0.408
- Obtain AMD Provisioning Console version 4.0.0.408 or later from AMD's official download channels
- Back up the current AMD Provisioning Console installation and configuration
- Install or upgrade to version 4.0.0.408
- Verify the installation directory permissions are correctly set after upgrade
- Test that the Provisioning Console functions normally with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-21958 — 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-21958 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