# CVE-2019-9510: Microsoft Windows RDP can bypass the Windows lock screen

> An attacker with local access to an RDP client can bypass the remote system's lock screen by triggering a network disconnect and reconnect, gaining unauthorized session access.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mpp6-gpg9-88j7

## What is CVE-2019-9510?

CVE-2019-9510 is a medium-severity authentication bypass vulnerability in Microsoft Windows 10, published on 15 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Microsoft Windows 10 1803 and Windows Server 2019 and later systems can allow authenticated RDP-connected clients to gain access to user sessions without needing to interact with the Windows lock screen. Should a network anomaly trigger a temporary RDP disconnect, Automatic Reconnection of the RDP session will be restored to an unlocked state, regardless of how the remote system was left. By interrupting network connectivity of a system, an attacker with access to a system being used as a Windows RDP client can gain access to a connected remote system, regardless of whether or not the remote system was locked. This issue affects Microsoft Windows 10, version 1803 and later, and Microsoft Windows Server 2019, version 2019 and later.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2019-9510?

It affects 2 products.


Products: Microsoft Windows 10, Microsoft Windows Server 2019.

## How do I fix CVE-2019-9510?

No fix has been published for CVE-2019-9510 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-9510 being exploited?

There is no known exploitation of CVE-2019-9510 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-2019-9510 and fix it if it is affected.

What it is: CVE-2019-9510 is a medium-severity authentication bypass vulnerability in Microsoft Windows 10, published on 15 Jan 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-2019-9510 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-2019-9510/ (Markdown: https://insights.sbomify.com/CVE-2019-9510/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-9510
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-9510
- OSV: https://osv.dev/vulnerability/CVE-2019-9510

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-9510/
Summaries are generated and may contain mistakes; the official description above is the record.