A use after free in cleanup_index in index.c in Halibut 1.2 allows an attacker to cause a segmentation fault or possibly have other unspecified impact via a crafted text document.
Weakness
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Halibut | Halibut_project | 1.2 (including) | 1.2 (including) |
| Halibut | Ubuntu | bionic | * |
| Halibut | Ubuntu | focal | * |
| Halibut | Ubuntu | impish | * |
| Halibut | Ubuntu | kinetic | * |
| Halibut | Ubuntu | lunar | * |
| Halibut | Ubuntu | mantic | * |
| Halibut | Ubuntu | oracular | * |
| Halibut | Ubuntu | plucky | * |
Potential Mitigations
References
- https://carteryagemann.com/halibut-case-study.html#poc-halibut-text-uaf
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CC7UZ7NRXDA7YSCSGWE2CBQM7OZS3K2R/
- https://carteryagemann.com/halibut-case-study.html#poc-halibut-text-uaf
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CC7UZ7NRXDA7YSCSGWE2CBQM7OZS3K2R/