CVE-2017-11728
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 decompileSETMEMBER) 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 · high confidenceA heap-based buffer over-read vulnerability exists in the OpCode function (called from decompileSETMEMBER) in util/decompile.c of Ming library version 0.4.8. The vulnerability is triggered when processing a crafted malicious file, leading to reading beyond allocated heap memory boundaries and causing 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.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 `dpkg -l | grep ming` or `pkg-config --modversion ming` to identify the installed version of the Ming library. Also check library files with `ldd` on linked binaries or examine `/usr/lib/x86_64-linux-gnu/libming*.so` files.Affected if The version reported is 0.4.8 exactly
-
Identify applications using libming decompilerSearch for binaries or applications that link to libming and specifically use the decompile functionality. Use `ldconfig -p | grep ming` to find linked libraries, and review application code for calls to decompileSETMEMBER or OpCode functions from util/decompile.c.Affected if Applications process SWF/Flash files using Ming's decompiler functions
-
Check for untrusted file processingReview logs, file access patterns, or application behavior to determine if the Ming library processes files from untrusted or user-supplied sources. Examine how files are passed to the decompiler API.Affected if The decompiler processes files from untrusted or crafted sources
-
Verify decompile module is loadedConfirm the util/decompile.c module is part of the deployed Ming build. Check if the application explicitly loads or calls decompilation functions by tracing library calls with `ltrace` or reviewing application dependencies.Affected if The decompilation module is actively used by the application
You are affected if Ming version 0.4.8 is installed AND your application uses the decompiler functionality to process potentially untrusted SWF/Flash 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 files with Ming 0.4.8 until a patched version is available. Apply any vendor updates or implement input validation to check file structure before passing to the decompiler.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11728 — 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-11728 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