CVE-2018-16461 Command Injection in libnmap
Critical 9.8
Published
Updated
Check this codebase for CVE-2018-16461 and fix it if it is affected.
What it is: CVE-2018-16461 is a critical vulnerability in libnmap, published on 30 Oct 2018.
Exploitation: There is no known exploitation of CVE-2018-16461 in the wild and no public exploit code.
Affected packages and fixed versions:
- libnmap (npm): affected all versions; fixed in 0.4.16
- libnmap (npm): affected all versions; fixed in 0.4.16
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-16461/ (Markdown: https://insights.sbomify.com/CVE-2018-16461/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2018-16461?
CVE-2018-16461 is a critical vulnerability in libnmap, published on 30 Oct 2018.
Official description
A command injection vulnerability in libnmapp package for versions <0.4.16 allows arbitrary commands to be executed via arguments to the range options.
Which versions are affected by CVE-2018-16461?
2 open source packages ship an affected version, including libnmap. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
libnmap npm | All versions | 0.4.16 |
libnmap npm | All versions | 0.4.16 |
Products include Libnmap Project Libnmap.
How do I fix CVE-2018-16461?
Upgrade libnmap to 0.4.16 or later.
Is CVE-2018-16461 being exploited?
There is no known exploitation of CVE-2018-16461 in the wild and no public exploit code.
Sources
Also known as GHSA-7g2w-6r25-2j7p.