Skip to content
Fencer Vulns
high 7.8

CVE-2017-11571 json

FontForge 20161012 is vulnerable to a stack-based buffer overflow in addnibble (parsettf.c) resulting in DoS or code execution via a crafte…

published 2017-07-23 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-3186

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

Summary

FontForge 20161012 is vulnerable to a stack-based buffer overflow in addnibble (parsettf.c) resulting in DoS or code execution via a crafted otf file.

Patch / fix

  • fontforge Debian 14, Debian 13, Debian 12 1:20170731~dfsg-1

debian advisories DEBIAN-CVE-2017-11571

  • fontforge Ubuntu 14.04 LTS 20120731.b-5ubuntu0.1
  • fontforge Ubuntu 16.04 LTS 20120731.b-7.1ubuntu0.1

ubuntu advisories UBUNTU-CVE-2017-11571

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

  • fontforge SLE Software Development Kit 12 SP4 20170731-11.8.1

suse advisories SUSE-SU-2019:2236-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-11571 updated cvss 3.3

fontforge: Stack-buffer overflow in addnibble function

  • Red Hat Enterprise Linux 6 fontforge Red Hat Enterprise Linux 7 fontforge
    affected: no fix planned “Will not fix”

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.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.