# GHSA-7r9x-hr76-jr96: Command Injection in giting

> Attackers can execute arbitrary code via unsanitized branch input in the pull function of the giting npm package.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2020

## What is GHSA-7r9x-hr76-jr96?

GHSA-7r9x-hr76-jr96 is a command injection vulnerability in giting, published on 4 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `gitting` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `exec` call, which may allow attackers to execute arbitrary code in the system. The `pull` function is vulnerable through the `branch` variable.

## Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

## Which versions are affected by GHSA-7r9x-hr76-jr96?

2 open source packages ship an affected version, including giting.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `giting` | npm | From 0.0.0 | None |
| `giting` | npm | From 0.0.0 | None |

## How do I fix GHSA-7r9x-hr76-jr96?

No fix has been published for GHSA-7r9x-hr76-jr96 yet. Limit exposure of the affected software until one is available.

## Is GHSA-7r9x-hr76-jr96 being exploited?

There is no known exploitation of GHSA-7r9x-hr76-jr96 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-7r9x-hr76-jr96 and fix it if it is affected.

What it is: GHSA-7r9x-hr76-jr96 is a command injection vulnerability in giting, published on 4 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-7r9x-hr76-jr96 in the wild and no public exploit code.

Affected packages and fixed versions:
- giting (npm): affected from 0.0.0; no fix listed
- giting (npm): affected from 0.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/GHSA-7r9x-hr76-jr96/ (Markdown: https://insights.sbomify.com/GHSA-7r9x-hr76-jr96/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-7r9x-hr76-jr96

---
From sbomify Insights: https://insights.sbomify.com/GHSA-7r9x-hr76-jr96/
Summaries are generated and may contain mistakes; the official description above is the record.