A security feature bypass vulnerability exists when a Windows Projected Filesystem improperly handles file redirections. An attacker who successfully exploited this vulnerability could delete a targeted file they would not have permissions to.
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability.
The security update addresses the vulnerability by correcting how Windows Projected Filesystem handle file redirections.
## Which versions are affected by CVE-2020-0805? It affects 2 products. Products: Microsoft Windows 10, Microsoft Windows Server 2016. ## How do I fix CVE-2020-0805? No fix has been published for CVE-2020-0805 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-0805 being exploited? There is no known exploitation of CVE-2020-0805 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft Windows 10 - [CVE-2015-2426](https://insights.sbomify.com/CVE-2015-2426/): Microsoft Windows Adobe Type Manager Library Remote Code Execution (high 8.8, exploited in the wild) - [CVE-2015-1769](https://insights.sbomify.com/CVE-2015-1769/): Microsoft Windows Mount Manager Privilege Escalation (medium 6.6, exploited in the wild) - [CVE-2020-1467](https://insights.sbomify.com/CVE-2020-1467/): Windows Hard Link Elevation of Privilege Vulnerability (critical 10.0) - [CVE-2021-26424](https://insights.sbomify.com/CVE-2021-26424/): Windows TCP/IP Remote Code Execution Vulnerability (critical 9.9) - [CVE-2021-28476](https://insights.sbomify.com/CVE-2021-28476/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-0805 and fix it if it is affected. What it is: CVE-2020-0805 is a medium-severity vulnerability in Microsoft Windows 10, published on 11 Sep 2020. 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-2020-0805 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-2020-0805/ (Markdown: https://insights.sbomify.com/CVE-2020-0805/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-0805 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-0805 - OSV: https://osv.dev/vulnerability/CVE-2020-0805 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-0805/ Summaries are generated and may contain mistakes; the official description above is the record.