# GHSA-g8vp-6hv4-m67c: Command Injection in entitlements


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Sep 2020

## What is GHSA-g8vp-6hv4-m67c?

GHSA-g8vp-6hv4-m67c is a vulnerability in entitlements, published on 11 Sep 2020. 

### Official description

Versions of `entitlements` prior to 1.3.0 are vulnerable to Command Injection. The package does not validate input on the `entitlements` function  and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.

## Recommendation

Upgrade to version 1.3.0 or later.

## Which versions are affected by GHSA-g8vp-6hv4-m67c?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `entitlements` | npm | All versions | 1.3.0 |
| `entitlements` | npm | All versions | 1.3.0 |

## How do I fix GHSA-g8vp-6hv4-m67c?

Upgrade entitlements to 1.3.0 or later.

## Is GHSA-g8vp-6hv4-m67c being exploited?

There is no known exploitation of GHSA-g8vp-6hv4-m67c in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g8vp-6hv4-m67c and fix it if it is affected.

What it is: GHSA-g8vp-6hv4-m67c is a vulnerability in entitlements, published on 11 Sep 2020. 
Exploitation: There is no known exploitation of GHSA-g8vp-6hv4-m67c in the wild and no public exploit code.

Affected packages and fixed versions:
- entitlements (npm): affected all versions; fixed in 1.3.0
- entitlements (npm): affected all versions; fixed in 1.3.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/GHSA-g8vp-6hv4-m67c/ (Markdown: https://insights.sbomify.com/GHSA-g8vp-6hv4-m67c/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g8vp-6hv4-m67c

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g8vp-6hv4-m67c/
Summaries are generated and may contain mistakes; the official description above is the record.