CVE-2022-26062
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 element in the Intel(R) Trace Analyzer and Collector before version 2021.6 for Intel(R) oneAPI HPC Toolkit 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 2021.6 contains an uncontrolled search path element vulnerability. The application uses an insecure path to locate files, allowing an authenticated local user to potentially place a malicious file in the search path before the legitimate file is found, enabling 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< 2021.6CVSS 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.
-
Identify installed Intel Trace Analyzer and Collector versionUse the system's package manager to list installed packages, or check the application binary with a version flag (e.g., itac --version, ittapi --version, or check the 'About' dialog in the GUI). On Windows, check Add/Remove Programs or the installation directory for version information.Affected if The installed version is any version prior to 2021.6 (for example, 2021.5, 2021.4, 2021.3, etc.)
-
Determine if application directory is writable by unprivileged usersCheck file system permissions on the Intel Trace Analyzer and Collector installation directory (commonly found under C:\Program Files\Intel or /opt/intel). Use 'icacls' on Windows or 'ls -la' on Linux to inspect permissions.Affected if The installation directory or any subdirectory has write permissions granted to standard users or the 'Users' group
-
Verify search path directories for write accessExamine environment variables such as PATH, LD_LIBRARY_PATH, and any application-specific path variables. Check each directory in the search path for world-writable or group-writable permissions.Affected if Any directory in the application's search path is writable by non-privileged users, allowing them to place a malicious file to be loaded before the legitimate file
A user is affected if Intel Trace Analyzer and Collector version is below 2021.6 AND the application's installation directory or search path contains writable locations accessible to unprivileged 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 · scoped2021.6
Update to Intel Trace Analyzer and Collector version 2021.6 or later. Until patched, ensure the application's directory and search paths are not writable by unprivileged users.
2021.6
- Download Intel Trace Analyzer and Collector version 2021.6 or later from the Intel website
- Uninstall any existing version of Intel Trace Analyzer and Collector
- Install the updated version 2021.6
- Verify the installation completed successfully
- Confirm the installed version is 2021.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26062 — 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-2022-26062 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