UprofApplication · Amd
CVE-2023-31366
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 · uneditedImproper input validation in AMD μProf could allow an attacker to perform a write to an invalid address, potentially 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 confidenceAMD μProf contains an improper input validation vulnerability that allows an attacker to trigger a write to an invalid memory address via specially crafted input. This can cause the application to crash or become unstable, resulting in denial of service.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify AMD μProf is installedSearch for amduprof or uprof executables in common installation paths such as C:\Program Files\AMD\uProf or C:\Program Files (x86)\AMD\uProf, or use system search commandsAffected if AMD μProf is found installed on the system
-
Determine installed versionRun the updriver or uprof command with version flag, typically 'uprof --version' or look for version information in the application directory or Windows Programs and FeaturesAffected if A version number is returned that is lower than 4.1.424, 4.2.816, or 4.2.845
-
Check if profiling functionality is enabledVerify the application is configured to accept external input or profiling sessions - the vulnerability triggers via specially crafted input during normal profiler operationAffected if The application accepts external/profiled application input and is not running in a completely isolated or read-only mode
The system is affected if AMD μProf is installed and the running version is below 4.1.424, 4.2.816, or 4.2.845, and the application accepts external input for profiling sessions.
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-supplied patch or update AMD μProf to the latest version that addresses this input validation vulnerability.
AMD μProf version 4.1.424 or later for the 4.1.x branch; or version 4.2.845 or later for the 4.2.x branch
- 1. Identify the currently installed AMD μProf version using 'uprof --version' or checking the application directory
- 2. If running version < 4.1.424 or < 4.2.816 (or < 4.2.845 on the 4.2 branch), download the latest fixed version from the official AMD website at amd.com/en/resources/developer-uprof.html
- 3. Uninstall the current AMD μProf installation
- 4. Install the updated version (4.1.424 or later for 4.1.x branch, or 4.2.845 or later for 4.2.x branch)
- 5. Verify the installation was successful by running 'uprof --version' to confirm the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Uprof
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31366 — 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-31366 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