How severe is GHSA-9hqj-38j2-5jgm?

No CVSS score has been assigned to GHSA-9hqj-38j2-5jgm yet. Review the advisory details and affected package list to assess your exposure.

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

GHSA-9hqj-38j2-5jgm affects the following packages: ascii-art (npm). Ecosystems affected: npm.

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

Update ascii-art to 1.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9hqj-38j2-5jgm is resolved across your whole dependency graph.

How do I detect GHSA-9hqj-38j2-5jgm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ascii-art, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9hqj-38j2-5jgm if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-9hqj-38j2-5jgm actively exploited in the wild?

No public exploit code has been indexed for GHSA-9hqj-38j2-5jgm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9hqj-38j2-5jgm published, and has it been updated?

GHSA-9hqj-38j2-5jgm was published on September 1, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Command Injection in ascii-artGHSA-9hqj-38j2-5jgm

GHSA-9hqj-38j2-5jgm is a remote code execution vulnerability in ascii-art. A fix is available for ascii-art — see the affected versions and patch details below.

Published

Sep 1, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

106other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

ascii-artnpm

781downloads / week

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ascii-art`	all versions	1.4.4`npm install ascii-art@1.4.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ascii-art, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ascii-art to 1.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9hqj-38j2-5jgm is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-9hqj-38j2-5jgm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works