# CVE-2022-45145: Command injection in n/a

> Attackers can execute arbitrary OS commands during package installation by exploiting escape characters in .egg files within the CHICKEN Scheme compiler.

- **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:** Yes
- **Published:** 10 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** CLEANSTART-2023-XN05686, GHSA-xvm4-qw2r-9jf6, UBUNTU-CVE-2022-45145

## What is CVE-2022-45145?

CVE-2022-45145 is a critical command injection vulnerability in n/a, published on 10 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

egg-compile.scm in CHICKEN 5.x before 5.3.1 allows arbitrary OS command execution during package installation via escape characters in a .egg file.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Call-Cc Chicken.

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

Upgrade to a fixed version.

## Is CVE-2022-45145 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-6310](https://insights.sbomify.com/CVE-2014-6310/): Memory corruption in n/a (critical 9.8)
- [CVE-2012-6125](https://insights.sbomify.com/CVE-2012-6125/): Denial of service in chicken (critical 9.8)
- [CVE-2016-6830](https://insights.sbomify.com/CVE-2016-6830/): Memory corruption in n/a (critical 9.8)
- [CVE-2013-2024](https://insights.sbomify.com/CVE-2013-2024/): Command injection in chicken (high 8.8)
- [CVE-2013-2075](https://insights.sbomify.com/CVE-2013-2075/): Memory corruption in chicken (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45145 is a critical command injection vulnerability in n/a, published on 10 Dec 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-45145 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-45145/ (Markdown: https://insights.sbomify.com/CVE-2022-45145/index.md)
```

## Sources

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

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