# GHSA-4859-gpc7-4j66: Command Injection in dot

> Attackers can execute arbitrary commands via template injection or prototype pollution in the dot library.

- **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:** 5 Jun 2019

## What is GHSA-4859-gpc7-4j66?

GHSA-4859-gpc7-4j66 is a command injection vulnerability in dot, published on 5 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of dot are vulnerable to Command Injection. The template compilation may execute arbitrary commands if an attacker can inject code in the template or if a Prototype Pollution-like vulnerability can be exploited to alter an Object's prototype.

## Which versions are affected by GHSA-4859-gpc7-4j66?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dot` | npm | All versions to 1.1.2 | None |
| `dot` | npm | All versions to 1.1.2 | None |

## How do I fix GHSA-4859-gpc7-4j66?

No fix has been published for GHSA-4859-gpc7-4j66 yet. Limit exposure of the affected software until one is available.

## Is GHSA-4859-gpc7-4j66 being exploited?

There is no known exploitation of GHSA-4859-gpc7-4j66 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4859-gpc7-4j66 and fix it if it is affected.

What it is: GHSA-4859-gpc7-4j66 is a command injection vulnerability in dot, published on 5 Jun 2019. 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-4859-gpc7-4j66 in the wild and no public exploit code.

Affected packages and fixed versions:
- dot (npm): affected all versions up to 1.1.2; no fix listed
- dot (npm): affected all versions up to 1.1.2; 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-4859-gpc7-4j66/ (Markdown: https://insights.sbomify.com/GHSA-4859-gpc7-4j66/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4859-gpc7-4j66

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4859-gpc7-4j66/
Summaries are generated and may contain mistakes; the official description above is the record.