CVE-2018-12155
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 · uneditedData leakage in cryptographic libraries for Intel IPP before 2019 update1 release may allow an authenticated 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 · moderate confidenceData leakage vulnerability in Intel Integrated Performance Primitives (IPP) cryptographic libraries prior to the 2019 update1 release may allow authenticated local users to potentially expose sensitive information through the flaw.
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< 2019= 2019CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Intel IPP installation directorySearch for 'ipp' or 'Intel IPP' in common installation paths such as C:\Program Files\Intel\ or /opt/intel/, and check for directories named 'ipp' or 'ippcp' (cryptographic primitives)Affected if Intel IPP is found in the system
-
Identify Intel IPP cryptographic library filesLook for library files with names containing 'ippcp' (Intel IPP Cryptographic Primitives) such as libippcp.so, ippcp.lib, or ippcp.dll depending on the operating systemAffected if ippcp cryptographic library files are present
-
Determine installed Intel IPP versionCheck version information of the ipp library files - right-click the DLL/SO file and select Properties > Details, or use a version inspection tool. Also check any version.txt or version.h files in the Intel IPP directoryAffected if Version is identified as less than 2019 update 1, or version 2019 without the update1 marker
-
Verify cryptographic functions are in useReview application dependencies or code that links to ippcp libraries. Check for import tables or linking configuration that references ippcp cryptographic functionsAffected if Applications are linked to or directly调用 Intel IPP cryptographic (ippcp) libraries
-
Check for sensitive data processingReview logs or application behavior to determine if the cryptographic library is used for encrypting, decrypting, hashing, or handling sensitive information such as passwords, keys, or private dataAffected if Intel IPP cryptographic functions process sensitive or confidential data in memory
User is affected if Intel IPP cryptographic libraries (ippcp) are installed with version 2019 or any version prior to 2019 update1, and those libraries process sensitive data in the environment.
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.
From vendor data2019
Update Intel IPP cryptographic libraries to version 2019 update1 or later to remediate the vulnerability.
- 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-2018-12155 — 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-2018-12155 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