# CVE-2016-7052: Null dereference in n/a

> Remote attackers can cause a denial of service via NULL pointer dereference in OpenSSL's CRL verification process.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2016-7052, DEBIAN-CVE-2016-7052, GHSA-9wm3-5vv7-j93j

## What is CVE-2016-7052?

CVE-2016-7052 is a high-severity vulnerability in Nodejs Node.js, published on 26 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

crypto/x509/x509_vfy.c in OpenSSL 1.0.2i allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) by triggering a CRL operation.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 3 products.


Products: Nodejs Node.js, Novell Suse Linux Enterprise Module for Web Scripting, Openssl Openssl.

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

Upgrade to a fixed version.

## Is CVE-2016-7052 being exploited?

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

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-7052 is a high-severity vulnerability in Nodejs Node.js, published on 26 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-7052 in the wild and no public exploit code.

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

## Sources

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

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