# CVE-2016-2182: The BN_bn2dec function in crypto/bn/bn_print.c in OpenSSL before 1.1.0 does not properly validate division results, which allows remote atta


- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 16 Sep 2016
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2016-2182, DEBIAN-CVE-2016-2182, GHSA-qc4g-43pw-wqh8, UBUNTU-CVE-2016-2182, USN-3087-2

## What is CVE-2016-2182?

CVE-2016-2182 is a critical vulnerability in Openssl Openssl, published on 16 Sep 2016. 

### Official description

The BN_bn2dec function in crypto/bn/bn_print.c in OpenSSL before 1.1.0 does not properly validate division results, which allows remote attackers to cause a denial of service (out-of-bounds write and application crash) or possibly have unspecified other impact via unknown vectors.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 6 products.


Products: Hp Icewall Federation Agent, Hp Icewall Mcrp, Hp Icewall Sso, Hp Icewall Sso Agent Option, Openssl Openssl, Oracle Linux.

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

Upgrade to a fixed version.

## Is CVE-2016-2182 being exploited?

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

## Other vulnerabilities in Openssl Openssl

- [CVE-2017-8945](https://insights.sbomify.com/CVE-2017-8945/): Open redirect in IceWall Federation Agent (medium 6.1)
- [CVE-2013-4820](https://insights.sbomify.com/CVE-2013-4820/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-2182 is a critical vulnerability in Openssl Openssl, published on 16 Sep 2016. 
Exploitation: There is no known exploitation of CVE-2016-2182 in the wild and no public exploit code.

Affected product: Openssl Openssl. 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-2182/ (Markdown: https://insights.sbomify.com/CVE-2016-2182/index.md)
```

## Sources

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

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