# CVE-2021-41316: Command injection in n/a

> An attacker with job editing permissions can inject arguments into the Nmap utility to overwrite arbitrary files as root on the Remote Collector.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-95jv-r6j9-p8xr

## What is CVE-2021-41316?

CVE-2021-41316 is a high-severity command injection vulnerability in n/a, published on 17 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Device42 Main Appliance before 17.05.01 does not sanitize user input in its Nmap Discovery utility. An attacker (with permissions to add or edit jobs run by this utility) can inject an extra argument to overwrite arbitrary files as the root user on the Remote Collector.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2021-41316?

It affects 1 product.


Products: Device42 Device42.

## How do I fix CVE-2021-41316?

No fix has been published for CVE-2021-41316 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41316 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41316 and fix it if it is affected.

What it is: CVE-2021-41316 is a high-severity command injection vulnerability in n/a, published on 17 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41316 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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