libming Ming
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in libming Ming.
By the Year
In 2026 there have been 0 vulnerabilities in libming Ming. Ming did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 5 | 6.50 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 2 | 0.00 |
It may take a day or so for new Ming vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent libming Ming Security Vulnerabilities
Ming 0.4.8 has an out-of-bounds read vulnerability in the function newVar_N() in decompile.c
CVE-2021-34342
6.5 - Medium
- March 10, 2022
Ming 0.4.8 has an out-of-bounds read vulnerability in the function newVar_N() in decompile.c which causes a huge information leak.
Out-of-bounds Read
Ming 0.4.8 has an out-of-bounds read vulnerability in the function decompileIF() in the decompile.c file
CVE-2021-34341
6.5 - Medium
- March 10, 2022
Ming 0.4.8 has an out-of-bounds read vulnerability in the function decompileIF() in the decompile.c file that causes a direct segmentation fault and leads to denial of service.
Out-of-bounds Read
Ming 0.4.8 has an out-of-bounds buffer access issue in the function decompileINCR_DECR() in decompiler.c file
CVE-2021-34340
6.5 - Medium
- March 10, 2022
Ming 0.4.8 has an out-of-bounds buffer access issue in the function decompileINCR_DECR() in decompiler.c file that causes a direct segmentation fault and leads to denial of service.
Memory Corruption
Ming 0.4.8 has an out-of-bounds buffer access issue in the function getString() in decompiler.c file
CVE-2021-34339
6.5 - Medium
- March 10, 2022
Ming 0.4.8 has an out-of-bounds buffer access issue in the function getString() in decompiler.c file that causes a direct segmentation fault and leads to denial of service.
Memory Corruption
Ming 0.4.8 has an out-of-bounds buffer overwrite issue in the function getName() in decompiler.c file
CVE-2021-34338
6.5 - Medium
- March 10, 2022
Ming 0.4.8 has an out-of-bounds buffer overwrite issue in the function getName() in decompiler.c file that causes a direct segmentation fault and leads to denial of service.
Memory Corruption
Ming (aka libming) 0.4.8 has a NULL pointer dereference in the function getString() in the decompile.c file in libutil.a.
CVE-2019-9113
- February 25, 2019
Ming (aka libming) 0.4.8 has a NULL pointer dereference in the function getString() in the decompile.c file in libutil.a.
Ming (aka libming) 0.4.8 has an out of bounds write vulnerability in the function strcpyext() in the decompile.c file in libutil.a.
CVE-2019-9114
- February 25, 2019
Ming (aka libming) 0.4.8 has an out of bounds write vulnerability in the function strcpyext() in the decompile.c file in libutil.a.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for libming Ming or by libming? Click the Watch button to subscribe.
