Out-of-bounds reads during instruction decoding 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 | Out-of-bounds read vulnerabilities in the pybddisasm Python bindings may disclose adjacent process memory during instruction decoding. The nd_decode function may read up to 15 bytes without checking the actual length of the supplied Python buffer. The nd_decode_ex, nd_decode_ex2, and nd_decode_with_context functions pass the caller-supplied buffer size to the decoder without validating it against the actual length of the Python buffer. Data read beyond the buffer may be exposed through nd_get_instrux_bytes, which returns a fixed-length list of 16 bytes. Exploitation requires an application to invoke the affected APIs with a short buffer or an oversized length and to expose the resulting bytes to an attacker. The pybddisasm package is no longer maintained. | |
| Title | Out-of-bounds reads during instruction decoding in pybddisasm | |
| Weaknesses | CWE-125 | |
| References |
| |
| Metrics |
cvssV4_0
|