CVE-2017-10976
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 · uneditedWhen SWFTools 0.9.2 processes a crafted file in ttftool, it can lead to a heap-based buffer over-read in the readBlock() function in lib/ttf.c.
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 · moderate confidenceSWFTools 0.9.2 ttftool contains a heap-based buffer over-read vulnerability in the readBlock() function in lib/ttf.c. When processing a specially crafted file, the function reads beyond the allocated heap buffer boundary, potentially allowing an attacker to read sensitive memory contents or cause a denial of service.
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= 0.9.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 if SWFTools is installedRun 'swftools -V' or 'swftools -version' to see installed version, or check package manager for swftools packageAffected if SWFTools version 0.9.2 is returned
-
Verify exact version numberCompare the installed version output to '0.9.2'. Some systems may show 0.9.2 with minor suffixes - confirm it is exactly 0.9.2Affected if Version shown is exactly 0.9.2
-
Check if ttftool binary existsRun 'which ttftool' or 'find /usr -name ttftool' to locate the ttftool executableAffected if ttftool binary is present on the system
-
Determine if ttftool processes untrusted inputReview any scripts, workflows, or automated processes that invoke ttftool. Check if they process files from untrusted or external sourcesAffected if ttftool is used to process files from untrusted or unknown sources
User is affected if SWFTools version 0.9.2 is installed AND ttftool is used to process files, especially from untrusted sources, because the vulnerability triggers when specially crafted font files are processed.
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 dataAvoid processing untrusted or unknown files with ttftool. Update to a patched version of SWFTools when available. If ttftool must be used, isolate it in a sandboxed environment with minimal privileges to limit the impact of potential exploitation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10976 — 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-10976 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