CVE-2023-31348 is a high severity DLL hijacking flaw, scored 7.3, in AMD uProf, a profiling tool for x86 applications. A local attacker could escalate privileges and run code. AMD bulletin AMD-SB-9001 names fixed builds: 4.2.845 for Windows, 4.2.850 for Linux and 4.2.816 for FreeBSD.
What's affected
The NVD record, dated 2024-08-13, says a DLL hijacking vulnerability in AMD uProf could allow an attacker to achieve privilege escalation, potentially resulting in arbitrary code execution. The weakness types are CWE-427 (uncontrolled search path element) and CWE-400 (uncontrolled resource consumption). The vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H. The record lists Windows, Linux and FreeBSD builds.
AMD's bulletin covers four uProf issues in total and does not give an affected version range. It tells customers to update to these builds instead.
AMD lists these fixed builds in bulletin AMD-SB-9001:
- Windows: AMDuProf-4.2.845.exe
- Linux: AMDuProf_Linux_x64_4.2.850.tar.bz2, or the 4.2-850 deb and rpm packages
- FreeBSD: AMDuProf_FreeBSD_x64_4.2.816.tar.bz2
The bulletin scores this CVE 7.3 (High), the same as NVD. AMD says severity varies by CVE across the four, so do not treat the other two as equal to this one. The bulletin was first published on 2024-08-13.
How to check if you're exposed
Open AMD uProf and read the version from its About dialog, or check the installer file name you used. Compare it with the fixed builds above for your operating system. Anything older than the listed build should be treated as affected, because AMD gives no earlier boundary.
DLL hijacking is mostly a Windows concern, so start with Windows workstations used by developers and performance engineers. List which users can write to the directories uProf loads files from, since that is how a search path flaw is normally reached.
The advisory does not describe a workaround, so updating is the fix.
What to do now
- Find machines with AMD uProf installed. Developer laptops and benchmark servers are the usual places.
- Download the fixed build for each operating system from AMD and install it over the old version.
- Remove old installers from shared drives so nobody reinstalls an affected build.
- On shared machines, restrict who can write to the uProf installation folder.
- Use standard user accounts for daily work so a planted file cannot gain elevated rights easily.
Why it matters
CWE-427 describes a program that searches several folders for a library and loads the first match. If an attacker can place a file in a folder searched earlier than the real one, the program runs it with its own privileges. That is why a profiler that runs elevated is a useful target for escalation.
The user interaction flag in the vector means someone must start the tool. Since the attacker needs a local account to begin, the risk is highest on shared build servers and lab machines. Safeguard offers a free in-browser dependency scan at gold.safeguard.sh/scan for the packages in your own code. It does not inspect installed desktop tools or device firmware, so those need a manual inventory.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is AMD uProf affected on every operating system?
The NVD record lists Windows, Linux and FreeBSD builds, and AMD publishes fixed builds for all three. Update whichever you use.
Is this exploited in the wild?
The record shows kev as false and AMD does not report exploitation. Updating is still the right step.
Sources
Last reviewed: 19 October 2026.