# CVE-2022-0514: Business Logic Errors in crater-invoice/crater


- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-7w5v-7f8j-hcgc

## What is CVE-2022-0514?

CVE-2022-0514 is a medium-severity vulnerability in crater-invoice/crater, published on 21 Mar 2022. 

### Official description

Business Logic Errors in GitHub repository crater-invoice/crater prior to 6.0.5.

Weakness: CWE-840

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

It affects 1 product.


Products: Craterapp Crater.

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

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

## Is CVE-2022-0514 being exploited?

There is no known exploitation of CVE-2022-0514 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-0372](https://insights.sbomify.com/CVE-2022-0372/): Cross-site Scripting (XSS) - Stored in crater-invoice/crater (high 7.6)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0514 is a medium-severity vulnerability in crater-invoice/crater, published on 21 Mar 2022. 
Exploitation: There is no known exploitation of CVE-2022-0514 in the wild and no public exploit code.

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

## Sources

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

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