CVE-2017-11705 json
A memory leak was found in the function parseSWF_SHAPEWITHSTYLE in util/parser.c in Ming 0.4.8, which allows attackers to cause a denial of…
published 2017-07-28 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-3315
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
A memory leak was found in the function parseSWF_SHAPEWITHSTYLE in util/parser.c in Ming 0.4.8, which allows attackers to cause a denial of service via a crafted file.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-11705 updated cvss 3.3
ming: Memory leak in parseSWF_SHAPEWITHSTYLE
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/libming/libming/issues/71 referenced PoC, tagged "exploit" by a source, unverified
- somevulnsofadlab.blogspot.jp http://somevulnsofadlab.blogspot.jp/2017/07/libmingmemory-leak-in.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-772 Missing Release of Resource after Effective Lifetime
References
-
github.com
/libming/libming/issues/71
exploit, third-party-advisory
-
somevulnsofadlab.blogspot.jp
/2017/07/libmingmemory-leak-in.html
exploit, third-party-advisory
Sources
- CVE List CVE-2017-11705
- NVD CVE-2017-11705
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.