Dislocker through 0.7.3 Heap Out-of-Bounds Read via BitLocker Metadata Dataset Size
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Aorimn | dislocker | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Aorimn | Dislocker |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.127% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aorimn
Aorimn dislocker |
|
| Vendors & Products |
Aorimn
Aorimn dislocker |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Dislocker through 0.7.3 contains a heap out-of-bounds read vulnerability in get_dataset() and get_next_datum() that never validate dataset and datum sizes against the metadata allocation. Attackers can craft a BitLocker volume image with inflated dataset or datum sizes that, when opened or mounted, crashes dislocker or discloses adjacent heap memory. | |
| Title | Dislocker through 0.7.3 Heap Out-of-Bounds Read via BitLocker Metadata Dataset Size | |
| Weaknesses | CWE-125 | |
| References |
|
|
| Metrics |
cvssV3_1
|