# CVE-2017-1000211: Use after free in n/a

> A use-after-free flaw in the Lynx text browser's HTML parser allows attackers to disclose memory contents.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** Yes
- **Published:** 17 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-1000211, DLA-1175-1, GHSA-6qv4-ghq2-3r52, MGASA-2017-0451, SUSE-SU-2017:3180-1, UBUNTU-CVE-2017-1000211

## What is CVE-2017-1000211?

CVE-2017-1000211 is a medium-severity use after free vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lynx before 2.8.9dev.16 is vulnerable to a use after free in the HTML parser resulting in memory disclosure, because HTML_put_string() can append a chunk onto itself.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lynx` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 2.8.6-146.3.1 |

Products: Lynx Project Lynx.

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

Upgrade to a fixed version.

## Is CVE-2017-1000211 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5002](https://insights.sbomify.com/CVE-2014-5002/): lynx doesn't properly sanitize user input and exposes database password to unauthorized users (high 7.8)
- [CVE-1999-1549](https://insights.sbomify.com/CVE-1999-1549/): Command injection in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1000211 is a medium-severity use after free vulnerability in n/a, published on 17 Nov 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-1000211 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-1000211/ (Markdown: https://insights.sbomify.com/CVE-2017-1000211/index.md)
```

## Sources

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

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