CVE-2017-11729
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 · uneditedA heap-based buffer over-read was found in the function OpCode (called from decompileINCR_DECR line 1440) in util/decompile.c in Ming 0.4.8, which allows attackers to cause a denial of service via a crafted file.
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 heap-based buffer over-read vulnerability exists in the OpCode function within util/decompile.c of Ming library version 0.4.8. The vulnerability is triggered through the decompileINCR_DECR code path (line 1440) when processing a crafted SWF file, leading to 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.4.8CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 installed Ming library versionRun `pkg-config --modversion ming` or check via package manager: `dpkg -l | grep ming` (Debian) or `rpm -q ming` (RPM-based). Also check header files for version defines in /usr/include/ming.h or similar.Affected if The version reported is exactly 0.4.8
-
Locate the vulnerable decompile.c source fileSearch for the file in the source tree or installed location: `find /usr -name 'decompile.c' 2>/dev/null` or check source packages. The vulnerable path is util/decompile.c around line 1440 in the decompileINCR_DECR function.Affected if The file exists and contains the decompileINCR_DECR function at approximately line 1440 without applied patches
-
Identify SWF processing tools using this libraryCheck for installed programs that depend on libming: `ldd $(which swftools 2>/dev/null) 2>/dev/null | grep ming` or `dpkg -rdepends libming` / `rpm -q --requires ming`. Common tools include swfdump, swfextract, and other Ming utilities.Affected if Any SWF decompilation or processing tools are installed and linked against unpatched Ming 0.4.8
-
Inspect the binary for the vulnerable functionUse `nm -C /usr/lib/libming.so 2>/dev/null | grep -i decompile` or `objdump -d /usr/lib/libming.so | grep -A5 decompileINCR_DECR` to examine if the function exists in the compiled library.Affected if The decompileINCR_DECR function symbol exists in the library binary without security modifications
You are affected if Ming library version 0.4.8 is installed and any SWF decompilation/processing tools using the vulnerable util/decompile.c code path are available to process untrusted files.
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 crafted SWF files with Ming 0.4.8 until an official patch is available; consider upgrading to a patched version of the library if released.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11729 — 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-11729 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