CVE-2022-25987
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 handling of Unicode encoding in source code to be compiled by the Intel(R) C++ Compiler Classic before version 2021.6 for Intel(R) oneAPI Toolkits before version 2022.2 may allow an unauthenticated user to potentially enable escalation of privilege via network 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 · moderate confidenceThe Intel C++ Compiler Classic before version 2021.6 (or oneAPI Toolkits before 2022.2) improperly handles Unicode encoding in source code being compiled. This could allow an unauthenticated attacker who can supply malicious source code to the compiler to achieve privilege escalation, likely through crafted Unicode characters that alter code interpretation during compilation.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Intel C++ Compiler Classic installationRun 'icpc --version' or 'icc -V' (for C++) from command line to display the compiler versionAffected if The displayed version is below 2021.6 (e.g., 2021.5, 2021.4, etc.)
-
Identify Intel oneAPI Toolkits installationRun 'icx --version' or check the Intel oneAPI installation directory for version informationAffected if The displayed version is below 2022.2 (e.g., 2022.1, 2022.0, etc.)
-
Verify build pipeline source handlingReview build pipeline configuration to determine if the compiler processes source code from untrusted or network-accessible locationsAffected if Build pipelines accept source code from untrusted network sources and use a vulnerable compiler version
You are affected if Intel C++ Compiler Classic is below version 2021.6 OR Intel oneAPI Toolkits is below version 2022.2, especially when processing source code from untrusted sources.
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
Upgrade Intel C++ Compiler Classic to version 2021.6 or later, or Intel oneAPI Toolkits to version 2022.2 or later. Review and audit any build pipelines that accept source code from untrusted network sources.
Intel C++ Compiler Classic 2021.6 or later; Intel oneAPI Toolkit 2022.2 or later
- Identify the currently installed version of Intel C++ Compiler Classic or Intel oneAPI Toolkit
- Download Intel C++ Compiler Classic version 2021.6 or later (or oneAPI Toolkit version 2022.2 or later) from the official Intel download center
- Install the updated compiler/toolkit following Intel's standard installation procedures
- Verify the installation was successful by checking the compiler version
- Recompile any existing projects to ensure they work with the updated compiler
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25987 — 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-25987 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