# CVE-2022-24376: Command Injection

> Attackers can execute arbitrary commands via the git-promise library due to an incomplete fix for a previous vulnerability.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-chj3-f7xw-367m

## What is CVE-2022-24376?

CVE-2022-24376 is a high-severity command injection vulnerability in git-promise, published on 10 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

All versions of package git-promise are vulnerable to Command Injection due to an inappropriate fix of a prior [vulnerability](https://security.snyk.io/vuln/SNYK-JS-GITPROMISE-567476) in this package. **Note:** Please note that the vulnerability will not be fixed. The README file was updated with a warning regarding this issue.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `git-promise` | npm | All versions to 1.0.0 | None |
| `git-promise` | npm | All versions to 1.0.0 | None |

Products: Git-Promise Project Git-Promise.

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

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

## Is CVE-2022-24376 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24376 is a high-severity command injection vulnerability in git-promise, published on 10 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24376 in the wild and no public exploit code.

Affected packages and fixed versions:
- git-promise (npm): affected all versions up to 1.0.0; no fix listed
- git-promise (npm): affected all versions up to 1.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-24376/ (Markdown: https://insights.sbomify.com/CVE-2022-24376/index.md)
```

## Sources

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

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