Skip to content
Fencer Vulns
medium 5.3

CVE-2017-1000211 json

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…

published 2017-11-17 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-1485

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

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.

Patch / fix

  • lynx Debian 14, Debian 13, Debian 12 2.8.9dev16-1

debian advisories DEBIAN-CVE-2017-1000211

  • lynx Ubuntu Pro 16.04 LTS 2.8.9dev8-4ubuntu1+esm1

ubuntu advisories UBUNTU-CVE-2017-1000211

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • lynx SLE Software Development Kit 11 SP4 2.8.6-146.3.1

suse advisories SUSE-SU-2017:3180-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-1000211 updated cvss 5.3

lynx: Use after free in HTML.c:HTML_put_string() can lead to memory disclosure

  • Red Hat Enterprise Linux 7 lynx
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 5 lynx Red Hat Enterprise Linux 6 lynx
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.73% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.