4.6
CVSSv3

CVE-2022-41099

Published: 09/11/2022 Updated: 10/03/2023
CVSS v3 Base Score: 4.6 | Impact Score: 3.6 | Exploitability Score: 0.9
VMScore: 0

Vulnerability Summary

BitLocker Security Feature Bypass Vulnerability

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

microsoft windows 10 1607

microsoft windows 10 -

microsoft windows 10 1809

microsoft windows 10 20h2

microsoft windows 10 21h1

microsoft windows 11 -

microsoft windows 10 21h2

microsoft windows 11 22h2

microsoft windows 10 22h2

Github Repositories

My starred Repos

Awesome Stars A curated list of my GitHub stars! Generated by starred Contents ai algorithm analytics android angular ansible api archlinux arduino artificial-intelligence automation awesome awesome-list aws azure backend bash bootstrap bot c chatgpt chatgpt-api chrome chrome-extension cli clojure code compiler computer-science cpp csharp css cybersecurity dart data-analys

A list of public attacks on BitLocker

BitLocker Attacks A list of public attacks on BitLocker Any public attack with the potential to attack BitLocker but where the exact method is still not public (like baton drop) is out of scope Most of the attacks are for where the VMK is sealed by TPM only, which is the default setting, and is what automatic BitLocker uses alongside recovery key escrow to a Microsoft account

WinRE Customization to apply patches, drivers and soon™ language packs

WinRE-Customization Customizes WinRE - recent updates can be found in the changelog This script applies patches and drivers Will resize recovery partition if required This script was initially created to automate remediation of CVE-2022-41099, however it can be used to patch WinRE monthly and automated as well The script will verify the size of your recovery partition and r

Script to update Windows Recovery Environment to patch against CVE-2022-41099

Update Windows RE - CVE-2022-41099 Script to update Windows Recovery Environment to patch against CVE-2022-41099 The script pulls the January CU for each build, mounts WinRE, updates it, saves WinRE, then verifies the build number matches what the January CU is Win10-21H1's last CU was Dec 2022 so that version pulls the Dec 22 CU Supported OS and Builds: Windows 11 (22H2

Update WINRE.WIM file to fix CVE-2022-41099

I take no Liability & Warranty on this script please fully test before use CVE-2022-41099-Fix Update WINREWIM file to fix CVE-2022-41099 REF: msrcmicrosoftcom/update-guide/vulnerability/CVE-2022-41099 Microsoft Catalog: wwwcatalogupdatemicrosoftcom/Searchaspx?q=kb5022282 You will need to create your own WINREwim file Tested with Intune, create

Patches CVE-2022-41099

WinRE-Patch Patches CVE-2022-41099 Original: githubcom/halsey51013/UpdateWindowsRE-CVE-2022-41099