CVE-2022-41099 BitLocker Security Feature Bypass Vulnerability
Medium 4.6
Published
Updated
Check this codebase for CVE-2022-41099 and fix it if it is affected.
What it is: CVE-2022-41099 is a medium-severity vulnerability in Microsoft Windows 10, published on 9 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41099 in the wild and no public exploit code.
Affected product: Microsoft Windows 10. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2022-41099/ (Markdown: https://insights.sbomify.com/CVE-2022-41099/index.md)
Attackers can bypass BitLocker security features on Windows, potentially exposing encrypted data or system integrity.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-41099?
CVE-2022-41099 is a medium-severity vulnerability in Microsoft Windows 10, published on 9 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
BitLocker Security Feature Bypass Vulnerability
Which versions are affected by CVE-2022-41099?
It affects 2 products.
Products include Microsoft Windows 10, Microsoft Windows 11.
How do I fix CVE-2022-41099?
No fix has been published for CVE-2022-41099 yet. Limit exposure of the affected software until one is available.
Is CVE-2022-41099 being exploited?
There is no known exploitation of CVE-2022-41099 in the wild and no public exploit code.
Public exploit code: 4 proofs of concept on GitHub.
Other vulnerabilities in Microsoft Windows 10
- CVE-2015-2426 Microsoft Windows Adobe Type Manager Library Remote Code Execution
- CVE-2015-1769 Microsoft Windows Mount Manager Privilege Escalation
- CVE-2020-1467 Windows Hard Link Elevation of Privilege Vulnerability
- CVE-2021-26424 Windows TCP/IP Remote Code Execution Vulnerability
- CVE-2021-28476 Windows Hyper-V Remote Code Execution Vulnerability
Sources
Also known as GHSA-859v-858p-559v.