# CVE-2023-30588: Denial of service in Node

> An attacker can cause a denial of service by providing an invalid public key to the X509Certificate API, forcing the Node.js process to terminate unexpectedly.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Nov 2023
- **Updated:** 3 Nov 2025
- **Also known as:** BIT-node-2023-30588, BIT-node-min-2023-30588, DEBIAN-CVE-2023-30588, GHSA-g526-x7vj-cfv6

## What is CVE-2023-30588?

CVE-2023-30588 is a medium-severity denial of service vulnerability in Nodejs Node.js, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect termination occurs making it susceptible to DoS attacks when the attacker could force interruptions of application processing, as the process terminates when accessing public key info of provided certificates from user code. The current context of the users will be gone, and that will cause a DoS scenario. This vulnerability affects all active Node.js versions v16, v18, and, v20.

## Which versions are affected by CVE-2023-30588?

2 open source packages ship an affected version, including node and node-min. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | From 16.0.0 | 16.20.1, 18.16.1, 20.3.1 |
| `node-min` | Bitnami | From 16.0.0 | 16.20.1, 18.16.1, 20.3.1 |

Products: Nodejs Node.js.

## How do I fix CVE-2023-30588?

Upgrade node to a fixed version for your release line: 16.20.1, 18.16.1 or 20.3.1.

## Is CVE-2023-30588 being exploited?

There is no known exploitation of CVE-2023-30588 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-2023-30588 and fix it if it is affected.

What it is: CVE-2023-30588 is a medium-severity denial of service vulnerability in Nodejs Node.js, published on 28 Nov 2023. 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-2023-30588 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected from 16.0.0; fixed in 16.20.1, 18.16.1, 20.3.1
- node-min (Bitnami): affected from 16.0.0; fixed in 16.20.1, 18.16.1, 20.3.1

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-2023-30588/ (Markdown: https://insights.sbomify.com/CVE-2023-30588/index.md)
```

## Sources

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

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