# CVE-2019-1681: Cisco Network Convergence System 1000 Series TFTP Directory Traversal Vulnerability

> Unauthenticated remote attackers can retrieve arbitrary files via TFTP directory traversal on Cisco NCS 1000 devices if the TFTP service is enabled.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 21 Feb 2019
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-6v3v-c95x-rpq9

## What is CVE-2019-1681?

CVE-2019-1681 is a high-severity path traversal vulnerability in Cisco Ios Xr, published on 21 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the TFTP service of Cisco Network Convergence System 1000 Series software could allow an unauthenticated, remote attacker to retrieve arbitrary files from the targeted device, possibly resulting in information disclosure. The vulnerability is due to improper validation of user-supplied input within TFTP requests processed by the affected software. An attacker could exploit this vulnerability by using directory traversal techniques in malicious requests sent to the TFTP service on a targeted device. An exploit could allow the attacker to retrieve arbitrary files from the targeted device, resulting in the disclosure of sensitive information. This vulnerability affects Cisco IOS XR Software releases prior to Release 6.5.2 for Cisco Network Convergence System 1000 Series devices when the TFTP service is enabled.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2019-1681?

It affects 1 product.


Products: Cisco Ios Xr.

## How do I fix CVE-2019-1681?

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

## Is CVE-2019-1681 being exploited?

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

## Other vulnerabilities in Cisco Ios Xr

- [CVE-2020-3118](https://insights.sbomify.com/CVE-2020-3118/): Cisco IOS XR Software Discovery Protocol Format String (high 8.8, exploited in the wild)
- [CVE-2020-3569](https://insights.sbomify.com/CVE-2020-3569/): Cisco IOS XR Software DVMRP Memory Exhaustion (high 8.6, exploited in the wild)
- [CVE-2020-3566](https://insights.sbomify.com/CVE-2020-3566/): Cisco IOS XR Software DVMRP Memory Exhaustion (high 8.6, exploited in the wild)
- [CVE-2010-3035](https://insights.sbomify.com/CVE-2010-3035/): Cisco IOS XR Border Gateway Protocol (BGP) Denial-of-Service (high 7.5, exploited in the wild)
- [CVE-2022-20821](https://insights.sbomify.com/CVE-2022-20821/): Cisco IOS XR Open Port (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1681 and fix it if it is affected.

What it is: CVE-2019-1681 is a high-severity path traversal vulnerability in Cisco Ios Xr, published on 21 Feb 2019. 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-2019-1681 in the wild and no public exploit code.

Affected product: Cisco Ios Xr. 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-2019-1681/ (Markdown: https://insights.sbomify.com/CVE-2019-1681/index.md)
```

## Sources

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

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