# CVE-2017-10685: Code injection in n/a

> A format string vulnerability in ncurses allows remote attackers to execute arbitrary code via crafted input.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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:** 29 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-10685, DEBIAN-CVE-2017-10685, GHSA-67w6-7r3q-87w7, UBUNTU-CVE-2017-10685

## What is CVE-2017-10685?

CVE-2017-10685 is a critical code injection vulnerability in n/a, published on 29 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In ncurses 6.0, there is a format string vulnerability in the fmt_entry function. A crafted input will lead to a remote arbitrary code execution attack.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2017-10685?

It affects 1 product.


Products: Invisible-Island Ncurses.

## How do I fix CVE-2017-10685?

Upgrade to a fixed version.

## Is CVE-2017-10685 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-10684](https://insights.sbomify.com/CVE-2017-10684/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-29491](https://insights.sbomify.com/CVE-2023-29491/): Memory corruption in n/a (high 7.8)
- [CVE-2017-16879](https://insights.sbomify.com/CVE-2017-16879/): Memory corruption in n/a (high 7.8)
- [CVE-2017-13728](https://insights.sbomify.com/CVE-2017-13728/): Denial of service in n/a (high 7.5)
- [CVE-2017-11112](https://insights.sbomify.com/CVE-2017-11112/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10685 and fix it if it is affected.

What it is: CVE-2017-10685 is a critical code injection vulnerability in n/a, published on 29 Jun 2017. 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-2017-10685 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-2017-10685/ (Markdown: https://insights.sbomify.com/CVE-2017-10685/index.md)
```

## Sources

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

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