# CVE-2022-42002: Path traversal in n/a

> Unauthenticated attackers can overwrite or delete arbitrary files via fileCreate and fileUpdate mutations, potentially leading to code execution.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 30 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-pc9q-654c-78w3

## What is CVE-2022-42002?

CVE-2022-42002 is a critical path traversal vulnerability in n/a, published on 30 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SonicJS through 0.6.0 allows file overwrite. It has the following mutations that are used for updating files: fileCreate and fileUpdate. Both of these mutations can be called without any authentication to overwrite any files on a SonicJS application, leading to Arbitrary File Write and Delete.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Sonicjs Sonicjs.

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

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

## Is CVE-2022-42002 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-33690](https://insights.sbomify.com/CVE-2023-33690/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42002 is a critical path traversal vulnerability in n/a, published on 30 Sep 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-42002 in the wild and no public exploit code.

Affected product: n/a. 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-2022-42002/ (Markdown: https://insights.sbomify.com/CVE-2022-42002/index.md)
```

## Sources

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

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