# GHSA-9hqj-38j2-5jgm: Command Injection in ascii-art


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

## What is GHSA-9hqj-38j2-5jgm?

GHSA-9hqj-38j2-5jgm is a vulnerability in ascii-art, published on 1 Sep 2020. 

### Official description

Versions of `ascii-art` before 1.4.4 are vulnerable to command injection. This is exploitable when user input is passed into the argument of the `ascii-art preview` command. 

Example Proof of concept:
`ascii-art preview 'doom"; touch /tmp/malicious; echo "'`

Given that the input is passed on the command line and none of the api methods are vulnerable to this,  the likely exploitation vector is when the ascii-art comment is being called programmatically using something like `execFile`.

## Recommendation

Update to version 1.4.4 or later.

## Which versions are affected by GHSA-9hqj-38j2-5jgm?

2 open source packages ship an affected version, including ascii-art.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ascii-art` | npm | All versions | 1.4.4 |
| `ascii-art` | npm | All versions | 1.4.4 |

## How do I fix GHSA-9hqj-38j2-5jgm?

Upgrade ascii-art to 1.4.4 or later.

## Is GHSA-9hqj-38j2-5jgm being exploited?

There is no known exploitation of GHSA-9hqj-38j2-5jgm in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9hqj-38j2-5jgm and fix it if it is affected.

What it is: GHSA-9hqj-38j2-5jgm is a vulnerability in ascii-art, published on 1 Sep 2020. 
Exploitation: There is no known exploitation of GHSA-9hqj-38j2-5jgm in the wild and no public exploit code.

Affected packages and fixed versions:
- ascii-art (npm): affected all versions; fixed in 1.4.4
- ascii-art (npm): affected all versions; fixed in 1.4.4

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-9hqj-38j2-5jgm/ (Markdown: https://insights.sbomify.com/GHSA-9hqj-38j2-5jgm/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9hqj-38j2-5jgm

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9hqj-38j2-5jgm/
Summaries are generated and may contain mistakes; the official description above is the record.