dbcve.org
Aim T Manageability ApiApplication · Amd

CVE-2023-31358

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 6.0.0.2234 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
A DLL hijacking vulnerability in the AMD Manageability API 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

This is a DLL hijacking vulnerability in the AMD Manageability API that allows an attacker to inject a malicious DLL that gets loaded by the vulnerable application, enabling privilege escalation from a lower-privileged context to achieve code execution with elevated privileges.

MitigationApply the vendor patch from AMD when available. If no patch is available, consider removing or disabling the AMD Manageability API component if unnecessary, and use application control mechanisms to restrict DLL loading from untrusted paths.

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
Aim T Manageability ApiApplication
Affected:< 6.0.0.2234

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/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. Identify if AMD Manageability API is installed
    Check for the presence of the AMD Manageability API component on the system. Look for AMD-related services or executables associated with the Amd Aim T Manageability Api. This may appear as a Windows service or a background process related to AMD utilities.
    Affected if The AMD Manageability API component is found installed on the system.
  2. Determine the installed version of Amd Aim T Manageability Api
    Locate the version information for the installed AMD Manageability API component. This may be found in the executable properties, installed program details, or via command-line tools that query installed software. Compare the version number against the affected range.
    Affected if The installed version is lower than 6.0.0.2234.
  3. Check if the AMD Manageability API service is running
    Verify whether the AMD Manageability API service or related background process is currently active. On Windows, use the Services console or task manager to check for AMD-related services.
    Affected if The service is running and the version is vulnerable.
  4. Identify DLL search path configuration
    Examine the DLL loading configuration and search paths used by the AMD Manageability API. Check for writable directories in the DLL search order that could allow an attacker to place a malicious DLL.
    Affected if The DLL search path includes user-writable directories and the service runs with elevated privileges.

The system is affected if Amd Aim T Manageability Api version lower than 6.0.0.2234 is installed and the service is running, creating an opportunity for DLL hijacking to achieve privilege escalation.

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

Apply the vendor patch from AMD when available. If no patch is available, consider removing or disabling the AMD Manageability API component if unnecessary, and use application control mechanisms to restrict DLL loading from untrusted paths.

Recommended fix High confidence

6.0.0.2234 or later

  1. 1. Identify the currently installed version of AMD Manageability API on the affected system
  2. 2. Navigate to the official AMD support website at www.amd.com to locate the latest version of the AMD Manageability API
  3. 3. Download AMD Manageability API version 6.0.0.2234 or later
  4. 4. Ensure the downloaded software is verified for authenticity (e.g., check digital signature)
  5. 5. Apply the upgrade following AMD's documented installation procedures
  6. 6. Restart any services or systems that rely on the AMD Manageability API after installation
  7. 7. Verify the installed version matches the expected fixed version (6.0.0.2234 or higher)

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

Fix this in Aim T Manageability Api Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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