dbcve.org
Integrated Performance Primitives CryptographyApplication · Intel

CVE-2022-26083

HIGH · 7.5 CVSS v3.1 Published 2025-02-14
Fix available
A fix is available. Upgrade to 2021.5 or later.
See remediation →
77/100
Remediation priority · High
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
Generation of weak initialization vector in an Intel(R) IPP Cryptography software library before version 2021.5 may allow an unauthenticated user to potentially enable information disclosure 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 confidence

Intel IPP Cryptography library before version 2021.5 contains a flaw in its initialization vector (IV) generation routine, producing weak or predictable IVs. This vulnerability could allow an unauthenticated attacker with local access to perform cryptanalysis on encrypted data, potentially exposing sensitive information.

MitigationUpgrade Intel IPP Cryptography library to version 2021.5 or later to obtain the fixed IV generation implementation.

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
Integrated Performance Primitives CryptographyApplication
Affected:< 2021.5

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

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. Locate Intel IPP Cryptography library files
    Search for library files named ippcp (e.g., libippcp.so on Linux, ippcp.dll on Windows) in common installation directories such as /opt/intel/ipp, /usr/local/lib, or C:\Program Files\Intel\IPP. Use 'find / -name "ippcp*" 2>/dev/null' on Linux or check Program Files directories on Windows.
    Affected if Library files are found with a version below 2021.5 or version cannot be determined.
  2. Determine installed library version
    Inspect the library file properties using system tools. On Windows, right-click the DLL and view Details for the Product Version. On Linux, use 'strings libippcp.so | grep -i version' or check any VERSION info embedded in the binary. Also check any version.txt or VERSION file in the installation directory.
    Affected if The detected version is less than 2021.5 (e.g., 2021.4, 2021.3, 2021.2, etc.).
  3. Check library package or installer version
    If installed via package manager (Linux) or installer, query the package database. On Linux, use 'dpkg -l | grep ipp' or 'rpm -qa | grep -i ipp'. On Windows, check Add/Remove Programs or the installed program list for 'Intel IPP' and note the version shown.
    Affected if The installed package version is listed as anything before 2021.5.
  4. Identify applications using the library
    Check for running processes or configured applications that link against ippcp. On Linux, use 'ldd' on suspected binaries or 'lsof | grep ippcp' to find open library handles. On Windows, use Process Explorer or Process Monitor to find processes loading ippcp.dll.
    Affected if Any application is actively using the Intel IPP Cryptography library version below 2021.5 for encryption operations.

Your environment is affected if the Intel IPP Cryptography library version installed on your system is lower than 2021.5 and any application is using it for cryptographic operations that rely on IV generation.

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 2021.5 or later
Fixed in 2021.5
Interim mitigation

Upgrade Intel IPP Cryptography library to version 2021.5 or later to obtain the fixed IV generation implementation.

Recommended fix High confidence

2021.5 or later

  1. 1. Identify all systems and applications using Intel(R) Integrated Performance Primitives (IPP) Cryptography library versions prior to 2021.5
  2. 2. Download Intel IPP Cryptography version 2021.5 or later from the official Intel website or repository
  3. 3. Replace the older vulnerable library binaries with the updated 2021.5 or newer version
  4. 4. Rebuild or recompile any applications statically linked against the old IPP Cryptography library
  5. 5. Verify the new library version is correctly loaded by checking the library version at runtime
  6. 6. Test cryptographic operations that rely on initialization vector generation to confirm correct behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Integrated Performance Primitives Cryptography Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26083 — 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-2022-26083 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