Libming vulnerabilities
We track 5 vulnerabilities in Libming products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on March 27, 2025.
Latest Libming vulnerabilities
- 7.5 High severity
Libming: Uncontrolled Resource Consumption
An out-of-memory error in the parseABC_STRING_INFO function of libming v0.4.8 allows attackers to cause a Denial of Service (DoS) due to allocator exhaustion.
- 7.5 High severity
Libming: Uncontrolled Resource Consumption
An out-of-memory error in the parseABC_NS_SET_INFO function of libming v0.4.8 allows attackers to cause a Denial of Service (DoS) due to allocator exhaustion.
- 8.2 High severity
Libming: Improper Clearing of Heap Memory Before Release
A memory leak has been identified in the parseSWF_SOUNDINFO function in util/parser.c of libming v0.4.8, which allows attackers to cause a denial of service via a crafted SWF file.
- 9.8 Critical severity
Libming: Buffer Copy without Checking Size of Input
Buffer Overflow vulnerability in libming version 0.4.8, allows attackers to execute arbitrary code and obtain sensitive information via parser.c component.
- 7.5 High severity
Libming: Buffer Copy without Checking Size of Input
libming 0.4.8 0.4.8 is vulnerable to Buffer Overflow. In getInt() in decompile.c unknown type may lead to denial of service. This is a different vulnerability than CVE-2018-9132 and CVE-2018-20427.