milliways-infosec/bitlocker-attacks
7
0
Fork 0
mirror of https://github.com/Wack0/bitlocker-attacks.git synced 2026-05-26 09:10:48 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
14 commits 1 branch 0 tags 25 MiB
Commit graph

14 commits

This branch
This branch
All branches
Author SHA1 Message Date
Rairii
10a32fdf66 yellowkey: correct documentation 
fstx is new and has nothing to do with NTFS filesystem transactions
 2026-05-18 17:08:18 +01:00
Rairii
b9f9cbf4cc let's drop another bitlocker 0day 
one 0day is already out there, another one won't change anything in the bitlocker security meta
 2026-05-18 10:40:18 +01:00
Rairii
119e03935c Add YellowKey 0day. 2026-05-15 13:22:01 +01:00
Rairii
db4bd6f319 add CVE-2025-48804 2025-08-09 21:09:36 +01:00
Rairii
8aa84a2181 add CrashXTS, thanks to @msuhanov :) 2025-02-14 14:45:39 +00:00
Rairii
284137490a added more vulns 2025-02-14 14:05:09 +00:00
zc
9e9182b923 push button decrypt: mention exploitable major windows versions now Nickel is known to work 2023-08-18 11:45:44 +01:00
zc
9e8472bf6b Revert "CVE-2022-41099: add more details, you have to patch the bitlocker metadata on-disk to "remove" any recovery keys first" 
This reverts commit 91b5504ed1.
 2023-05-16 18:36:52 +01:00
zc
91b5504ed1 CVE-2022-41099: add more details, you have to patch the bitlocker metadata on-disk to "remove" any recovery keys first 
thanks to feardot for the help, I was initially testing with just a VMK sealed by TPM, no recovery key (which can be done using manage-bde)
 2023-05-15 21:47:39 +01:00
zc
473c206bfb add writeup of CVE-2022-41099 after bindiffing 2023-05-04 21:55:07 +01:00
zc
b553a1c6a3 add more details about CVE-2022-29127, the MSRC page now gives credits 2023-05-02 16:36:57 +01:00
zc
ee00d23786 add a word 2023-05-01 22:16:44 +01:00
zc
541f6c783e initial commit of list 2023-05-01 22:15:19 +01:00
zc
b271b8711c Add .gitattributes, .gitignore, and LICENSE.txt. 2023-05-01 11:41:12 +01:00