UprofApplication · Amd
CVE-2023-31348
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 · uneditedA DLL hijacking vulnerability in AMD μProf 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 confidenceA DLL hijacking vulnerability exists in AMD μProf where the application loads Dynamic Link Libraries from an unsecured path, allowing a local attacker to place a malicious DLL in a location where μProf will load it. This can lead to privilege escalation and arbitrary code execution with the privileges of the running process.
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
UprofApplication
< 4.1.424< 4.2.816< 4.2.845CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm AMD μProf is installedLook for AMD μProf in the system: check Program Files/AMD uProf or search for 'uProf' or 'AMD μProf' in the start menu or installed programs listAffected if AMD μProf software is present on the system
-
Identify the installed μProf versionRight-click the μProf executable (commonly uProf.exe or uProf_App.exe), select Properties, then look at the Version tab for the Product Version fieldAffected if The version number is less than 4.1.424, OR less than 4.2.816, OR less than 4.2.845
-
Check for writable directories in the μProf installation pathNavigate to the directory where μProf is installed, right-click each subfolder, go to Properties > Security, and verify which users have Write permissionAffected if Non-privileged users have Write permission to any directory in μProf's DLL search path
-
Verify DLL search path securityRun Sysinternals Process Monitor (procmon) with a filter for Process Name = uProf.exe, then start μProf and observe which DLL paths it attempts to load; check if any are user-writable locations like the application directory or TEMPAffected if μProf loads DLLs from directories that non-privileged users can modify
The system is affected if AMD μProf is installed with a version below 4.1.424, 4.2.816, or 4.2.845 AND non-privileged users can write to directories in μProf's DLL search path.
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.
dbcve · scoped4.1.4244.2.8164.2.845
Apply the vendor patch from AMD when available. Until then, restrict user write access to directories in μProf's DLL search path and avoid running μProf from user-controlled locations.
AMD μProf 4.2.845 (or 4.1.424+ for 4.1.x branch)
- 1. Identify the currently installed AMD μProf version by checking the application or using 'uprof --version' if available
- 2. Determine which version branch you are running (4.1.x or 4.2.x)
- 3. Download the latest AMD μProf version from the official AMD website at www.amd.com
- 4. Uninstall the current version of AMD μProf through Windows Control Panel or the application's uninstaller
- 5. Install the fixed version: for 4.1.x branch use version 4.1.424 or higher; for 4.2.x branch use version 4.2.845 or higher
- 6. Verify the installation was successful and the version matches the expected fixed release
- 7. Restart any running applications that use μProf to ensure they load the updated libraries
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Uprof
Scoped from the published advisory
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31348 — 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-31348 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