# CVE-2018-16716: Path traversal in n/a

> Attackers can read arbitrary files or delete files via path traversal in the NCBI ToolBox CGI script, leading to information disclosure or data loss.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pcqx-g45m-pmqh

## What is CVE-2018-16716?

CVE-2018-16716 is a critical path traversal vulnerability in n/a, published on 2 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability exists in viewcgi.c in the 2.0.7 through 2.2.26 legacy versions of the NCBI ToolBox, which may result in reading of arbitrary files (i.e., significant information disclosure) or file deletion via the nph-viewgif.cgi query string.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Nih Ncbi Toolbox.

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

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

## Is CVE-2018-16716 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-16716 exists.

Public exploit code:

- NCBI ToolBox - Directory Traversal (nuclei): http/cves/2018/CVE-2018-16716.yaml

## Other vulnerabilities in n/a

- [CVE-2018-16717](https://insights.sbomify.com/CVE-2018-16717/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-16718](https://insights.sbomify.com/CVE-2018-16718/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16716 is a critical path traversal vulnerability in n/a, published on 2 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-16716 exists.

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

## Sources

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

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