# CVE-2022-0372: Cross-site Scripting (XSS) - Stored in crater-invoice/crater

> Stored Cross-Site Scripting in Crater Invoice allows attackers to inject malicious scripts, potentially leading to session hijacking or code execution.

- **Severity:** High 7.6 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Jan 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6vfw-74wr-3chh

## What is CVE-2022-0372?

CVE-2022-0372 is a high-severity cross-site scripting vulnerability in crater-invoice/crater, published on 27 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site Scripting (XSS) - Stored in Packagist bytefury/crater prior to 6.0.2.

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

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

2 open source packages ship an affected version, including bytefury/crater. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bytefury/crater` | Packagist | All versions | 6.0.0 |
| `bytefury/crater` | Packagist | All versions | 6.0.0 |

Products: Craterapp Crater.

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

Upgrade bytefury/crater to 6.0.0 or later.

## Is CVE-2022-0372 being exploited?

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

## Other vulnerabilities in crater-invoice/crater

- [CVE-2021-4080](https://insights.sbomify.com/CVE-2021-4080/): Unrestricted Upload of File with Dangerous Type in crater-invoice/crater (high 8.8)
- [CVE-2022-0203](https://insights.sbomify.com/CVE-2022-0203/): Improper Access Control in crater-invoice/crater (high 7.5)
- [CVE-2023-46865](https://insights.sbomify.com/CVE-2023-46865/): Code injection in n/a (high 7.2)
- [CVE-2022-1032](https://insights.sbomify.com/CVE-2022-1032/): Insecure deserialization of not validated module file in crater-invoice/crater (high 7.2)
- [CVE-2022-1033](https://insights.sbomify.com/CVE-2022-1033/): Unrestricted Upload of File with Dangerous Type in crater-invoice/crater (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0372 is a high-severity cross-site scripting vulnerability in crater-invoice/crater, published on 27 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-0372 in the wild and no public exploit code.

Affected packages and fixed versions:
- bytefury/crater (Packagist): affected all versions; fixed in 6.0.0
- bytefury/crater (Packagist): affected all versions; fixed in 6.0.0

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

## Sources

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

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