CVE-2023-31349 is a high severity flaw, scored 7.3, caused by incorrect default permissions in the AMD uProf installation directory. It could let a local attacker escalate privileges and run arbitrary code. AMD bulletin AMD-SB-9001 lists fixed builds: 4.2.845 on Windows, 4.2.850 on Linux, 4.2.816 on FreeBSD.
What's affected
The NVD record, dated 2024-08-13, says incorrect default permissions in the AMD uProf installation directory could allow an attacker to achieve privilege escalation, potentially resulting in arbitrary code execution. The weakness is CWE-276. The vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, and the record lists Windows, Linux and FreeBSD.
This CVE sits in the same AMD bulletin as CVE-2023-31348, a DLL hijacking issue with the same score. AMD gives no affected range, only the builds to update to.
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
AMD and NVD agree on 7.3 (High). No source says the flaw is exploited in the wild, and the record is not in the CISA catalog.
How to check if you're exposed
Read the uProf version in the application and compare it with the builds above. Then check the folder permissions on the installation directory, which is where this weakness lives.
On Windows, open the properties of the uProf install folder and look at the Security tab. Ordinary users should not hold write or modify rights on program folders. On Linux or FreeBSD, list the directory with ls -ld and ls -l and check for group or world writable bits.
Updating to the fixed build is the supported remedy. Do not rely only on changing permissions by hand, because the advisory does not describe that as a fix.
What to do now
- Locate every machine with uProf and note its version.
- Install the fixed build for the operating system from AMD.
- After updating, confirm the install folder is writable only by administrators or root.
- Add uProf to the software inventory you review each quarter.
- Remove copies of old installers from build images and golden VM templates, so new machines do not start out vulnerable.
Why it matters
CWE-276 is a setup mistake, not a coding trick. An installer gives a folder permissions that are too open, so someone without admin rights can change files that a privileged process later runs. The program is fine until the folder is not.
Findings like this are easy to miss because nothing in a package manifest shows them. A tool installed once by hand can sit on a machine for years. Treat developer tooling the way you treat servers: keep a list, know the version and retire what you do not use.
Quick check
What is the fix?
Update to the fixed build AMD names for your operating system: 4.2.845 on Windows, 4.2.850 on Linux or 4.2.816 on FreeBSD, per AMD-SB-9001.
Does the attacker need an account?
Yes. The vector is local with low privileges, and a user must start the tool.
Sources
Last reviewed: 19 October 2026.