libming 0.4.8 decompile.c decompileDELETE SWF File use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libming 0.4.8 and classified as problematic. Affected by this vulnerability is the function decompileDELETE of the file decompile.c. The manipulation as part of SWF File results in use after free.
This vulnerability is reported as CVE-2018-8964. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in libming 0.4.8 (Programming Tool Software). It has been classified as problematic. Affected is the function decompileDELETE of the file decompile.c. The manipulation as part of a SWF File leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on availability. CVE summarizes:
In libming 0.4.8, the decompileDELETE function of decompile.c has a use-after-free. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted swf file.
The bug was discovered 03/22/2018. The weakness was disclosed 03/23/2018 (Website). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2018-8964 since 03/23/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-114969, VDB-114970 and VDB-114971 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://github.com/libming/libming/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/22/2018 🔍03/23/2018 🔍
03/23/2018 🔍
03/23/2018 🔍
03/24/2018 🔍
02/24/2023 🔍
Sources
Product: github.comAdvisory: 130
Status: Not defined
CVE: CVE-2018-8964 (🔍)
GCVE (CVE): GCVE-0-2018-8964
GCVE (VulDB): GCVE-100-114972
See also: 🔍
Entry
Created: 03/24/2018 08:49Updated: 02/24/2023 07:17
Changes: 03/24/2018 08:49 (59), 01/16/2020 10:44 (1), 02/24/2023 07:17 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.