# CVE-2023-31361: Privilege escalation in AIM-T (AMD Integrated Management Technology) software

> An attacker can exploit DLL hijacking in AMD AIM-T to escalate privileges and execute arbitrary code on the affected system.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-2mpx-hg3q-3wq8

## What is CVE-2023-31361?

CVE-2023-31361 is a high-severity vulnerability in AIM-T (AMD Integrated Management Technology) software, published on 11 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A DLL hijacking vulnerability in AMD Integrated Management Technology (AIM-T) Manageability Service could allow an attacker to achieve privilege escalation potentially resulting in arbitrary code execution.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2023-31361?


## How do I fix CVE-2023-31361?

No fix has been published for CVE-2023-31361 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-31361 being exploited?

There is no known exploitation of CVE-2023-31361 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31361 and fix it if it is affected.

What it is: CVE-2023-31361 is a high-severity vulnerability in AIM-T (AMD Integrated Management Technology) software, published on 11 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-31361 in the wild and no public exploit code.

Affected product: AIM-T (AMD Integrated Management Technology) software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-31361/ (Markdown: https://insights.sbomify.com/CVE-2023-31361/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-31361
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-31361
- OSV: https://osv.dev/vulnerability/CVE-2023-31361

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-31361/
Summaries are generated and may contain mistakes; the official description above is the record.