# CVE-2022-25921: Arbitrary Code Execution

> Attackers can execute arbitrary code via unsanitized input in the morgan-json Node.js library due to unsafe use of the Function constructor.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 29 Aug 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-fwv4-6mxc-x5h3

## What is CVE-2022-25921?

CVE-2022-25921 is a high-severity code injection vulnerability in morgan-json, published on 29 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of package morgan-json are vulnerable to Arbitrary Code Execution due to missing sanitization of input passed to the Function constructor.

## Which versions are affected by CVE-2022-25921?

2 open source packages ship an affected version, including morgan-json. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `morgan-json` | npm | All versions to 1.1.0 | None |
| `morgan-json` | npm | All versions to 1.1.0 | None |

Products: Morgan-Json Project Morgan-Json.

## How do I fix CVE-2022-25921?

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

## Is CVE-2022-25921 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25921 and fix it if it is affected.

What it is: CVE-2022-25921 is a high-severity code injection vulnerability in morgan-json, published on 29 Aug 2022. 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-2022-25921 in the wild and no public exploit code.

Affected packages and fixed versions:
- morgan-json (npm): affected all versions up to 1.1.0; no fix listed
- morgan-json (npm): affected all versions up to 1.1.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-2022-25921/ (Markdown: https://insights.sbomify.com/CVE-2022-25921/index.md)
```

## Sources

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

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