dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-30133

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Windows Point-to-Point Protocol (PPP) 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 · moderate confidence

This is a remote code execution vulnerability in Windows Point-to-Point Protocol (PPP), a legacy protocol used for establishing direct connections between two nodes. An unauthenticated attacker could exploit this to execute arbitrary code on affected Windows systems with elevated privileges, potentially leading to complete system compromise.

MitigationApply the Microsoft security updates for CVE-2022-30133 immediately. Until patches are applied, consider disabling PPP if not required and restricting network access to vulnerable systems.

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 data
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 1607= 1809
Windows 11Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions= 20h2
Windows Server 2019Operating system
Affected:all versions

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Windows version is affected
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build number
    Affected if The system runs Windows 10 any version, Windows 11 any version, Windows 7 any version, Windows 8.1, Windows Server 2008/2012/2016/2019 any version
  2. Identify if PPP-related services exist
    Check for the presence of Remote Access Service or RRAS components. Run 'sc query' or check Services.msc for 'Routing and Remote Access (RRAS)' or 'Remote Access Auto Connection Manager' services
    Affected if Any PPP-related services are installed on the system
  3. Determine if PPP functionality is enabled
    Check if the system has any dial-up connections, RAS bindings, or VPN configurations that use PPP. Inspect network connections via 'ncpa.cpl' and check for legacy dial-up adapters or RAS devices
    Affected if Any PPP-based connections, dial-up adapters, or RAS configurations exist on the system
  4. Check for active PPP listening endpoints
    Use 'netstat -an' or 'netsh interface show' to enumerate active network interfaces and listening ports associated with RAS or PPP daemons
    Affected if The system has active PPP or RAS listeners accepting connections

The system is likely affected if it runs any supported Windows version from the affected list and has PPP/RRAS components installed or enabled, regardless of whether they are actively configured for incoming connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security updates for CVE-2022-30133 immediately. Until patches are applied, consider disabling PPP if not required and restricting network access to vulnerable systems.

Recommended fix Moderate confidence
  1. Apply the relevant Windows security update for CVE-2022-30133 from Microsoft Windows Update or Microsoft Update Catalog
  2. If using Windows Server, apply the update through Windows Server Update Services (WSUS) or Microsoft Update
  3. After installation, restart the affected system as prompted to complete the remediation
  4. Verify the update installed successfully by checking installed updates or using the Get-HotFix PowerShell cmdlet

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30133 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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