# CVE-2023-49210: openssl npm package vulnerable to command execution

> The deprecated node-openssl package allows command injection via the verb field, enabling arbitrary code execution for users still relying on this unsupported library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-75w2-qv55-x7fv

## What is CVE-2023-49210?

CVE-2023-49210 is a critical command injection vulnerability in n/a, published on 23 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The openssl (aka node-openssl) NPM package through 2.0.0 was characterized as "a nonsense wrapper with no real purpose" by its author, and accepts an opts argument that contains a verb field (used for command execution). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

2 open source packages ship an affected version, including openssl. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl` | npm | All versions to 2.0.0 | None |
| `openssl` | npm | All versions to 2.0.0 | None |

Products: Node-Openssl Project Node-Openssl.

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

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

## Is CVE-2023-49210 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-16064](https://insights.sbomify.com/CVE-2017-16064/): node-openssl is malware (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49210 and fix it if it is affected.

What it is: CVE-2023-49210 is a critical command injection vulnerability in n/a, published on 23 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-49210 in the wild and no public exploit code.

Affected packages and fixed versions:
- openssl (npm): affected all versions up to 2.0.0; no fix listed
- openssl (npm): affected all versions up to 2.0.0; no fix listed

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

## Sources

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

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