CVE-2010-4259
Published Dec 7, 2010 · Updated Oct 23, 2026
Original summary
Normalized public record · Updated Oct 23, 2026
Stack-based buffer overflow in FontForge 20100501 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a long CHARSET_REGISTRY header in a BDF font file.
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Stack-based buffer overflow in FontForge 20100501 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a long CHARSET_REGISTRY header in a BDF font file.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- 20%
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- 45162 ↗
- [oss-security] 20101202 Re: CVE Request -- FontForge: Stack-based buffer overflow by processing specially-crafted CHARSET_REGISTRY font file header ↗
- bugs.debian.org ↗
- DSA-2253 ↗
- FEDORA-2010-18577 ↗
- 42577 ↗
- FEDORA-2010-18573 ↗
- [oss-security] 20101202 CVE Request -- FontForge: Stack-based buffer overflow by processing specially-crafted CHARSET_REGISTRY font file header ↗
- bugzilla.redhat.com ↗
- 15732 ↗
- ADV-2010-3200 ↗
Record history
Published Dec 7, 2010 · Last refreshed Oct 23, 2026