CVE-2023-21543
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWindows Layer 2 Tunneling Protocol (L2TP) Remote Code Execution Vulnerability
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · low confidenceThis is a remote code execution vulnerability in Windows Layer 2 Tunneling Protocol (L2TP), a VPN protocol built into Windows. The vulnerability allows an attacker to execute arbitrary code on affected Windows systems via specially crafted L2TP packets, likely through a buffer overflow or similar memory corruption in the L2TP implementation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows versionRun `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to identify the installed Windows version and build numberAffected if The version matches any of these: Windows 10 1607, 1809, 20h2, 21h2, 22h2; Windows 11 21h2, 22h2; or Windows 7 (all versions)
-
Identify if L2TP is enabledOpen Control Panel > Network and Sharing Center > Change adapter settings. Look for network adapters with "L2TP" or "Layer 2 Tunneling Protocol" in the name, or check RAS connections via `netsh ras show`Affected if Any L2TP-based VPN connection or dial-up interface is present or was previously configured on the system
-
Check Routing and Remote Access service statusRun `services.msc` and locate "Routing and Remote Access (RRAS)" service, or run `netsh routing ip show` to see if L2TP/IPsec routing is configuredAffected if The RRAS service is running or L2TP/IPsec routing is enabled in the system routing configuration
-
Verify L2TP/IPsec registry configurationCheck registry key `HKLM\SYSTEM\CurrentControlSet\Services\RasMan\Parameters\IPsec` for L2TP/X.509 or L2TP/PSK configurations, or inspect `HKLM\SOFTWARE\Policies\Microsoft\Windows\L2TP` if presentAffected if L2TP/IPsec policies are defined in registry indicating L2TP is permitted or configured on the system
The system is likely affected if it runs any affected Windows version listed above AND has L2TP/IPsec enabled, configured, or was previously set up as an L2TP client or server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the relevant Microsoft security updates for this CVE to all affected Windows systems. If L2TP is not required in the environment, consider disabling the L2TP/IPsec feature to reduce the attack surface.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21543 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-21543 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data