CVE-2017-5436
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn out-of-bounds write in the Graphite 2 library triggered with a maliciously crafted Graphite font. This results in a potentially exploitable crash. This issue was fixed in the Graphite 2 library as well as Mozilla products. This vulnerability affects Thunderbird < 52.1, Firefox ESR < 45.9, Firefox ESR < 52.1, and Firefox < 53.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn out-of-bounds write vulnerability exists in the Graphite 2 font rendering library. When a maliciously crafted Graphite font is processed, the vulnerability triggers an out-of-bounds memory write, leading to a potentially exploitable crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.0= 6.0= 7.0= 6.0= 7.0= 6.0= 7.0= 7.3= 7.4= 7.3= 7.4= 7.5= 6.0= 7.0< 45.9.0< 53.0= 52.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Graphite 2 library version on DebianRun `dpkg -l libgraphite2-3` or `dpkg -l | grep graphite` to list installed Graphite 2 packages and their versionsAffected if The installed version is lower than the fixed version (1:1.3.6-1+deb8u1 for Debian 8) or if the package is present on Debian 8.0
-
Check Graphite 2 package version on RHELRun `rpm -qa | grep -i graphite` or `yum list installed graphite2` to list installed Graphite-related packages and versionsAffected if The package is present on RHEL 6.0, 6.x, 7.0, or 7.x versions (specifically 6.0, 7.0, 7.3, 7.4, 7.5 as listed)
-
Check Mozilla Firefox versionRun `firefox --version` or check Help > About Firefox in the browser to determine the installed Firefox versionAffected if Firefox version is less than 45.9.0, less than 53.0, or exactly 52.0 (all vulnerable)
-
Determine if Graphite font support is actively usedCheck for presence of .grs (Graphite Smart Font) files in system font directories (`ls /usr/share/fonts/*/grs* 2>/dev/null`) or user font folders, or check if applications load Graphite-enabled fontsAffected if Graphite fonts (.grs files) are present and the Graphite 2 library is used to render them, which triggers the vulnerability when a malicious font is processed
You are affected if you have a vulnerable Graphite 2 library version on Debian 8.0 or RHEL 6.0-7.5, or run Firefox versions less than 45.9.0, less than 53.0, or exactly 52.0, and process Graphite fonts with the library.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data45.9.053.0
Update Graphite 2 library to the patched version, or upgrade affected Mozilla products (Thunderbird to 52.1+, Firefox ESR to 45.9+/52.1+, Firefox to 53+) to incorporate the fixes.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5436 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5436 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data