LiveActive security incident?Get immediate response
CVE Record

CVE-2017-11570: FontForge 20161012 is vulnerable to a buffer over-read in umodenc (parsettf.c) resulting in DoS or code exe...

FontForge 20161012 is vulnerable to a buffer over-read in umodenc (parsettf.c) resulting in DoS or code execution via a crafted otf file.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

FontForge 20161012 can mishandle a crafted OTF font file. If a vulnerable system processes such a file, the reported impact is denial of service or possible code execution. Business urgency depends on whether FontForge is used on untrusted fonts, especially in automated upload, conversion, or publishing workflows.

Executive priority

Prioritize this where FontForge handles external fonts or runs in automated production workflows. If FontForge is only used manually on trusted files, urgency is lower, but the code execution claim warrants timely verification and upgrade planning.

Technical view

The CVE describes a buffer over-read in FontForge 20161012, in umodenc within parsettf.c, triggered by a crafted OTF file. The public bundle provides no CVSS score, CWE mapping, affected CPEs, or confirmed fixed version. Treat exposure as input-driven: risk rises when OTF parsing is reachable from external or low-trust sources.

Likely exposure

Likely exposure is limited to systems running FontForge 20161012 or embedded workflows that invoke it to parse OTF files. Highest concern is server-side font processing, CI asset pipelines, design automation, or user-uploaded font handling.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation requires a crafted OTF file being processed by the vulnerable FontForge build. Public evidence in the bundle is limited to the CVE record and referenced GitHub issue.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPE, fixed version, or exploit-status confirmation appears in the supplied bundle. Analysis should remain tied to FontForge 20161012, parsettf.c umodenc, and crafted OTF input unless further vendor or issue details are reviewed.

Mitigation direction

  • Inventory FontForge installations and identify any 20161012 builds.
  • Avoid processing untrusted OTF files with affected FontForge versions.
  • Check FontForge project guidance and release notes for the appropriate fixed version.
  • Isolate or disable automated FontForge workflows that ingest external fonts until reviewed.

Validation and detection

  • Confirm whether FontForge 20161012 is installed on workstations, servers, containers, or build images.
  • Map workflows that parse OTF files from uploads, customers, vendors, or public repositories.
  • Review crash logs around FontForge OTF parsing and font conversion jobs.
  • Verify remediation against official FontForge guidance before closing the finding.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-11570 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.