# CVE-2018-16462: Command Injection in apex-publish-static-files

> Attackers can execute arbitrary shell commands via malicious arguments in the apex-publish-static-files npm module.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9jm3-5835-537m

## What is CVE-2018-16462?

CVE-2018-16462 is a critical command injection vulnerability in apex-publish-static-files, published on 30 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A command injection vulnerability in the apex-publish-static-files npm module version <2.0.1 which allows arbitrary shell command execution through a maliciously crafted argument.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2018-16462?

2 open source packages ship an affected version, including apex-publish-static-files. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apex-publish-static-files` | npm | All versions | 2.0.1 |
| `apex-publish-static-files` | npm | All versions | 2.0.1 |

Products: Apex-Publish-Static-Files Project Apex-Publish-Static-Files.

## How do I fix CVE-2018-16462?

Upgrade apex-publish-static-files to 2.0.1 or later.

## Is CVE-2018-16462 being exploited?

There is no known exploitation of CVE-2018-16462 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16462 and fix it if it is affected.

What it is: CVE-2018-16462 is a critical command injection vulnerability in apex-publish-static-files, published on 30 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16462 in the wild and no public exploit code.

Affected packages and fixed versions:
- apex-publish-static-files (npm): affected all versions; fixed in 2.0.1
- apex-publish-static-files (npm): affected all versions; fixed in 2.0.1

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/CVE-2018-16462/ (Markdown: https://insights.sbomify.com/CVE-2018-16462/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-16462
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-16462
- OSV: https://osv.dev/vulnerability/CVE-2018-16462

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-16462/
Summaries are generated and may contain mistakes; the official description above is the record.