# CVE-2022-0748: Arbitrary Code Execution

> Attackers can execute arbitrary JavaScript code by providing malicious markdown input to the post-loader 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:** 17 Mar 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-66ww-999q-mffq, SNYK-JS-POSTLOADER-2403737

## What is CVE-2022-0748?

CVE-2022-0748 is a critical code injection vulnerability in post-loader, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The package post-loader from 0.0.0 are vulnerable to Arbitrary Code Execution which uses a markdown parser in an unsafe way so that any javascript code inside the markdown input files gets evaluated and executed.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `post-loader` | npm | From 0.0.0 | None |
| `post-loader` | npm | From 0.0.0 | None |

Products: Post-Loader Project Post-Loader.

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

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

## Is CVE-2022-0748 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0748 is a critical code injection vulnerability in post-loader, published on 17 Mar 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-0748 in the wild and no public exploit code.

Affected packages and fixed versions:
- post-loader (npm): affected from 0.0.0; no fix listed
- post-loader (npm): affected from 0.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-2022-0748/ (Markdown: https://insights.sbomify.com/CVE-2022-0748/index.md)
```

## Sources

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

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