Use-after-free in INSTRUX structure members in pybddisasm
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Bitdefender | pybddisasm | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Bitdefender | Pybddisasm |
|
Vendor Solution
Discontinue use of the unmaintained pybddisasm package. No fixed release will become available.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.105% probability within 30 days)
| Link | Providers |
|---|---|
| https://pypi.org/project/pybddisasm/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Bitdefender
Bitdefender pybddisasm |
|
| Vendors & Products |
Bitdefender
Bitdefender pybddisasm |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A use-after-free vulnerability in the pybddisasm Python bindings affects structure-valued members of INSTRUX objects. These members are exposed through Python objects that reference memory owned by the parent INSTRUX object. A retained reference to a member does not keep the parent allocation alive. Accessing the member after the parent INSTRUX object has been freed therefore accesses freed memory. Depending on how the member is used and whether the freed allocation has been reused, this may expose process memory or cause the Python process to crash. Exploitation requires an application to retain and subsequently access a member reference after the parent object has been freed. The pybddisasm package is no longer maintained. | |
| Title | Use-after-free in INSTRUX structure members in pybddisasm | |
| Weaknesses | CWE-416 | |
| References |
| |
| Metrics |
cvssV4_0
|