Uninitialized INSTRUX contents returned after decoding failure 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 of uninitialized memory vulnerability in the pybddisasm Python bindings may disclose process memory when instruction decoding fails. The nd_decode, nd_decode_ex, nd_decode_ex2, and nd_decode_with_context functions may return an INSTRUX object whose contents have not been initialized after an unsuccessful decoding operation, including failures caused by invalid parameters. Accessing members of the returned object may expose residual process memory. Exploitation requires an application to access and expose the returned object contents after a decoding failure. The pybddisasm package is no longer maintained. | |
| Title | Uninitialized INSTRUX contents returned after decoding failure in pybddisasm | |
| Weaknesses | CWE-457 | |
| References |
| |
| Metrics |
cvssV4_0
|