dbcve.org
UprofApplication · Amd

CVE-2023-31349

HIGH · 7.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 4.1.424 / 4.2.816 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Incorrect default permissions in the AMD μProf 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 confidence

Incorrect default permissions in the AMD μProf installation directory allow unprivileged users to modify executables, DLLs, or configuration files that are subsequently loaded by higher-privileged processes, enabling local privilege escalation to arbitrary code execution.

MitigationApply restrictive NTFS permissions to the AMD μProf installation directory, removing write access for standard users and limiting modification rights to administrators only.

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
Affected:< 4.1.424< 4.2.816< 4.2.845

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate AMD μProf installation directory
    Check the default installation path (typically C:\Program Files\AMD\uProf or C:\Program Files (x86)\AMD\uProf) or look in the Windows registry under HKLM\SOFTWARE\AMD\uProf for the InstallPath value
    Affected if The software is installed in a location accessible to standard users
  2. Identify installed AMD μProf version
    Right-click the uProf.exe or uProf_Analysis.exe file in the installation folder, select Properties, and check the Product Version field on the Details tab. Alternatively, run 'wmic product where "name like '%uProf%'" get version'
    Affected if The version number is lower than 4.1.424, 4.2.816, or 4.2.845 (or if version cannot be determined but the software is present)
  3. Check NTFS permissions on the installation directory
    Right-click the AMD μProf installation folder, go to Properties > Security tab, and examine the permissions for Users or standard user accounts. Click Edit > Permissions to see the Allow column for Write permission
    Affected if The Users group or standard user accounts have Write or Modify permissions granted on the installation directory

A user is affected if AMD μProf is installed with a version below 4.1.424/4.2.816/4.2.845 AND standard (non-admin) users have Write or Modify access to the installation directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.1.424 / 4.2.816 / 4.2.845 or later
Fixed in 4.1.4244.2.8164.2.845
Interim mitigation

Apply restrictive NTFS permissions to the AMD μProf installation directory, removing write access for standard users and limiting modification rights to administrators only.

Recommended fix Moderate confidence

AMD μProf 4.2.845 or later (or 4.1.424+ for the 4.1.x branch)

  1. Identify the currently installed AMD μProf version
  2. Download the latest AMD μProf version from the official AMD website (www.amd.com)
  3. Ensure you have administrator privileges before uninstalling the current version
  4. Uninstall the existing AMD μProf installation
  5. Install the updated version (4.1.424 or higher for the 4.1.x branch, or 4.2.845 or higher for the 4.2.x branch)
  6. Verify the installation completed successfully
  7. Confirm the new version is running with corrected default permissions
Caveat Review release notes for any changes to profiling capabilities or system requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Uprof Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31349 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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