# CVE-2016-8100: Intel Integrated Performance Primitives (aka IPP) Cryptography before 9.0.4 makes it easier for local users to discover RSA private keys via


- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hq3g-g9jf-v8mf

## What is CVE-2016-8100?

CVE-2016-8100 is a medium-severity vulnerability in n/a, published on 10 Oct 2016. 

### Official description

Intel Integrated Performance Primitives (aka IPP) Cryptography before 9.0.4 makes it easier for local users to discover RSA private keys via a side-channel attack.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-8100?

It affects 1 product.


Products: Intel Integrated Performance Primitives.

## How do I fix CVE-2016-8100?

No fix has been published for CVE-2016-8100 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-8100 being exploited?

There is no known exploitation of CVE-2016-8100 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-12155](https://insights.sbomify.com/CVE-2018-12155/): Information disclosure in Intel Integrated Performance Primitives (medium 5.5)
- [CVE-2024-28952](https://insights.sbomify.com/CVE-2024-28952/): Privilege escalation in Intel(R) IPP software for Windows (medium 5.4)
- [CVE-2024-28887](https://insights.sbomify.com/CVE-2024-28887/): Privilege escalation in Intel(R) IPP software (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8100 and fix it if it is affected.

What it is: CVE-2016-8100 is a medium-severity vulnerability in n/a, published on 10 Oct 2016. 
Exploitation: There is no known exploitation of CVE-2016-8100 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-8100/ (Markdown: https://insights.sbomify.com/CVE-2016-8100/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-8100
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-8100
- OSV: https://osv.dev/vulnerability/CVE-2016-8100

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-8100/
Summaries are generated and may contain mistakes; the official description above is the record.