CVE-2024-28172
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 · uneditedUncontrolled search path for some Intel(R) Trace Analyzer and Collector software before version 2022.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
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 · high confidenceIntel Trace Analyzer and Collector before version 2022.1 contains an uncontrolled search path vulnerability (DLL hijacking). The application loads DLLs from locations that an authenticated local attacker can write to, allowing them to plant malicious DLLs that execute with the application's privileges, leading to local privilege escalation.
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< 2024.1.0< 2022.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check if Intel Trace Analyzer and Collector is installedLook for the application in the system registry under HKLM\SOFTWARE\Intel\Trace Analyzer or check Program Files for Intel Trace Analyzer directoriesAffected if The application is found on the system
-
Determine the installed version of Intel Trace Analyzer and CollectorRight-click on the main executable (such as itac.exe or traceanalyzer.exe) in the installation directory, select Properties, and check the File Version fieldAffected if The version shown is earlier than 2022.1 (for example, 2021.x or earlier)
-
Check if Intel OneAPI HPC Toolkit is installedLook in the system registry under HKLM\SOFTWARE\Intel\OneAPI or check for Intel OneAPI directories in Program FilesAffected if Intel OneAPI HPC Toolkit is present on the system
-
Determine the version of Intel OneAPI HPC Toolkit if installedCheck the version information of the HPC Toolkit components or check the Intel OneAPI installation metadataAffected if The version is earlier than 2024.1.0
-
Verify if the application loads DLLs from user-writable locationsUse process monitoring tools or check the application configuration to identify DLL search paths and whether any point to directories with write permissions for low-privilege usersAffected if DLLs are loaded from directories writable by non-admin users (this condition enables the DLL hijacking vulnerability)
You are affected if Intel Trace Analyzer and Collector version is below 2022.1 or Intel OneAPI HPC Toolkit version is below 2024.1.0, AND the application loads DLLs from directories writable by authenticated local users.
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 · scoped2022.12024.1.0
Upgrade Intel Trace Analyzer and Collector to version 2022.1 or later to obtain the vendor patch.
OneAPI HPC Toolkit 2024.1.0 or later; Trace Analyzer And Collector 2022.1 or later
- Identify the currently installed version of Intel(R) OneAPI HPC Toolkit
- Identify the currently installed version of Intel(R) Trace Analyzer And Collector
- If using OneAPI HPC Toolkit, upgrade to version 2024.1.0 or later
- If using Trace Analyzer And Collector, upgrade to version 2022.1 or later
- Verify the upgrade was successful by checking the installed version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28172 — 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-2024-28172 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