CVE-2023-31360
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 Integrated Management Technology (AIM-T) Manageability Service 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 confidenceAMD AIM-T Manageability Service installs with overly permissive file system permissions in its installation directory, allowing unprivileged users to modify executable files. An attacker with local access could replace service binaries or DLLs 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.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify AMD AIM-T service is installedOpen Services console (services.msc) and look for 'AMD AIM-T Manageability Service' or check registry at HKLM\SYSTEM\CurrentControlSet\Services\AIM-T for presenceAffected if The service exists in the system
-
Locate the AIM-T installation directoryCheck the service binary path in registry at HKLM\SYSTEM\CurrentControlSet\Services\AIM-T\ImagePath, or search for 'aimt' folder under C:\Program Files\AMDAffected if AIM-T installation directory is found on the system
-
Inspect NTFS permissions on the AIM-T directoryRight-click the AIM-T installation folder in File Explorer, go to Properties > Security tab, and review the permissions. Alternatively, run: icacls "<AIMT directory>" to list all access control entriesAffected if Users group,Authenticated Users,or other non-admin principals have Write or FullControl permissions on the directory
-
Check executable file permissions for modification accessRun: icacls "<AIMT directory>\*.exe" and icacls "<AIMT directory>\*.dll" to see which users can modify, write, or delete binariesAffected if Non-admin users have Modify, Write, or FullControl rights to service executables or DLLs
-
Verify if standard users can write to the directory treeAs a standard (non-admin) user, attempt to create a test file in the AIM-T directory: echo test > "<AIMT directory>\test.txt" (remove after test)Affected if Non-privileged users successfully create files in the AIM-T installation directory
A system is affected if AMD AIM-T Manageability Service is installed and non-administrative users have write or modify permissions on the service's installation directory or its 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.
From vendor dataApply restrictive NTFS permissions to the AIM-T installation directory, ensuring only administrators can write to executable locations. Remove unnecessary permissions for standard users and verify service binary integrity.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31360 — 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-2023-31360 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