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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Aorimn dislocker
Default version status: unaffected
0 to ≤ 0.7.3affected
References
- https://github.com/Aorimn/dislocker/commit/9158e9e41dd669b360cbc53cc18ccae729b67b48 ↗
- https://github.com/Aorimn/dislocker/blob/v0.7.3/src/metadata/metadata.c#L764-L790 ↗
- https://github.com/Aorimn/dislocker/blob/v0.7.3/src/metadata/datums.c#L589-L640 ↗
- https://github.com/Aorimn/dislocker ↗
- https://www.vulncheck.com/advisories/dislocker-through-0.7.3-heap-out-of-bounds-read-via-bitlocker-metadata-dataset-size ↗