dbcve.org
UprofApplication · Amd

CVE-2023-31341

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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
Insufficient validation of the Input Output Control (IOCTL) input buffer in AMD μProf may allow an authenticated attacker to cause an out-of-bounds write, potentially causing a Windows® OS crash, resulting in denial of service.

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

AMD μProf contains an insufficient validation vulnerability in its IOCTL input buffer handling. An authenticated attacker can exploit this to trigger an out-of-bounds write, causing a Windows OS crash and resulting in denial of service.

MitigationApply the AMD μProf security update/patch provided by AMD to fix the IOCTL input validation vulnerability. Until the patch is available, restrict access to trusted authenticated users 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Check if AMD μProf is installed
    Open Windows Settings > Apps > Installed apps and search for 'AMD μProf' or 'AMDuProf', or check Program Files for the AMDuProf directory
    Affected if AMD μProf is present on the system
  2. Determine installed AMD μProf version
    Run 'AMDuProfCLI --version' from command line if available, or check Add/Remove programs for the version number
    Affected if Version is below 4.1.424, or between 4.1.424 and 4.2.816, or between 4.2.816 and 4.2.845 (all versions before 4.2.845 are affected)
  3. Verify vulnerable driver component exists
    Check for the AMDuProf.sys driver file in the AMD μProf installation directory (commonly in Program Files/AMD/AMDuProf or similar)
    Affected if The AMDuProf.sys driver file exists and the software version is in the affected range
  4. Confirm IOCTL handler is accessible
    Verify the AMD μProf service is running and accessible by authenticated users - check Windows services for 'AMDuProf' service status
    Affected if Service runs with elevated privileges and is accessible to standard authenticated users

If AMD μProf is installed with any version below 4.2.845 (including all versions below 4.1.424 and between 4.1.424-4.2.816), the system is vulnerable to this IOCTL validation flaw that can crash Windows when exploited by an authenticated user.

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 the AMD μProf security update/patch provided by AMD to fix the IOCTL input validation vulnerability. Until the patch is available, restrict access to trusted authenticated users only.

Recommended fix Moderate confidence

AMD μProf version 4.2.845 or later (or the latest available version)

  1. 1. Check the currently installed AMD μProf version by opening the application or checking the installed programs list in Windows Settings
  2. 2. Navigate to the official AMD website and locate the AMD μProf download page
  3. 3. Download the latest available version of AMD μProf (recommended: version 4.2.845 or later)
  4. 4. Close any running instances of AMD μProf before installation
  5. 5. Run the installer with administrative privileges
  6. 6. Follow the installation wizard prompts to complete the upgrade
  7. 7. Verify the new version is installed correctly after installation completes
Caveat No major breaking changes typically expected for developer profiling tools; minor changes to UI or features may occur

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-31341 — 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-31341 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