# GHSA-4q8f-5xxj-946r: Command Injection in addax

> Authenticated attackers can execute arbitrary system commands via unvalidated input in the presignPath function of the addax library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-4q8f-5xxj-946r?

GHSA-4q8f-5xxj-946r is a command injection vulnerability in addax, published on 3 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Versions of `addax` prior to 1.1.0 are vulnerable to Command Injection. The package does not validate user input on the `presignPath` function which receives input directly from the API endpoint. Exploiting the vulnerability requires authentication. This may allow attackers to run arbitrary commands in the system.

## Recommendation

Upgrade to version 1.1.0 or later.

## Which versions are affected by GHSA-4q8f-5xxj-946r?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `addax` | npm | All versions | 1.1.0 |
| `addax` | npm | All versions | 1.1.0 |

## How do I fix GHSA-4q8f-5xxj-946r?

Upgrade addax to 1.1.0 or later.

## Is GHSA-4q8f-5xxj-946r being exploited?

There is no known exploitation of GHSA-4q8f-5xxj-946r in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4q8f-5xxj-946r and fix it if it is affected.

What it is: GHSA-4q8f-5xxj-946r is a command injection vulnerability in addax, published on 3 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-4q8f-5xxj-946r in the wild and no public exploit code.

Affected packages and fixed versions:
- addax (npm): affected all versions; fixed in 1.1.0
- addax (npm): affected all versions; fixed in 1.1.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-4q8f-5xxj-946r/ (Markdown: https://insights.sbomify.com/GHSA-4q8f-5xxj-946r/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4q8f-5xxj-946r

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4q8f-5xxj-946r/
Summaries are generated and may contain mistakes; the official description above is the record.