CVE-2017-9927
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 · uneditedIn SWFTools 2013-04-09-1007 on Windows, png2swf allows remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted file, related to a "Read Access Violation starting at image00000000_00400000+0x000000000001b5fe."
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 confidenceA memory corruption vulnerability in png2swf (part of SWFTools 2013-04-09-1007 on Windows) allows remote attackers to cause a denial of service or possibly achieve unspecified impact via a specially crafted PNG file. The vulnerability manifests as a Read Access Violation during PNG processing, indicating improper bounds checking when parsing image data.
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= 2013-04-09-1007CVSS 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.
-
Locate the png2swf executableSearch for png2swf.exe (Windows) or png2swf (Linux) in common installation directories such as C:\Program Files\SWFTools or /usr/bin/, or use 'where png2swf' (Windows) or 'which png2swf' (Linux) to find it in system PATHAffected if png2swf executable exists on the system
-
Determine the SWFTools versionRun 'png2swf --version' or check the executable properties/details for the build date. The affected version is identified as 2013-04-09-1007Affected if The version reported is 2013-04-09-1007 exactly, indicating an unpatched installation
-
Verify the installation dateCheck the file creation/modification timestamp of the png2swf executable, or check the installer used to deploy SWFToolsAffected if The binary was installed around April 2013 and has not been updated
-
Check for automated conversion workflowsReview any scripts, scheduled tasks, or applications that invoke png2swf to process PNG files, particularly from untrusted sourcesAffected if png2swf is actively used to process PNG files from external or untrusted sources
You are affected if png2swf from SWFTools version 2013-04-09-1007 is present and used to process PNG files, since the vulnerability requires this specific vulnerable version and the png2swf component to be invoked.
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 PNG files with png2swf. If a patched version of SWFTools is available, upgrade immediately. Implement input validation and file type verification for any automated conversion workflows.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9927 — 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-9927 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