CVE-2022-41081: Windows Point-to-Point Tunneling Protocol Remote Code Execution Vulnerability

Published Oct 11, 2022
·
Updated

Windows Point-to-Point Tunneling Protocol Remote Code Execution Vulnerability. This CVE ID is unique from CVE-2022-22035, CVE-2022-24504, CVE-2022-30198, CVE-2022-33634, CVE-2022-38000, CVE-2022-38047.

Affected Software

60 affected componentsFixes available
Microsoft Windows 10
Microsoft Windows 10=20h2
Microsoft Windows 10=21h1
Microsoft Windows 10=21h2
Microsoft Windows 10=1607
Microsoft Windows 10=1809
Microsoft Windows 11
Microsoft Windows 11
Microsoft Windows 11=22h2
Microsoft Windows 11=22h2
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows RT 8.1
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Microsoft Windows Server 2022
Microsoft Windows Server 2012 R2<6.3.9600.20625
6.3.9600.20625
Microsoft Windows Server 2012<6.2.9200.23920
6.2.9200.23920
Microsoft Windows Server 2008 R2<6.1.7601.26174
6.1.7601.26174
Microsoft Windows Server 2012 R2<6.3.9600.20625
6.3.9600.20625
Microsoft Windows Server 2012<6.2.9200.23920
6.2.9200.23920
Microsoft Windows Server 2008 R2<6.1.7601.26174
6.1.7601.26174
Microsoft Windows Server 2008<6.0.6003.21721
6.0.6003.21721
Microsoft Windows Server 2008<6.0.6003.21721
6.0.6003.21721
Microsoft Windows Server 2008<6.0.6003.21721
6.0.6003.21721
Microsoft Windows Server 2008<6.0.6003.21721
6.0.6003.21721
Microsoft Windows RT 8.1<6.3.9600.20625
6.3.9600.20625
Microsoft Windows 8.1 for x64-based systems<6.3.9600.20625
6.3.9600.20625
Microsoft Windows 7<6.1.7601.26174
6.1.7601.26174
Microsoft Windows 8.1 for 32-bit systems<6.3.9600.20625
6.3.9600.20625
Microsoft Windows 7<6.1.7601.26174
6.1.7601.26174
Microsoft Windows Server 2016<10.0.14393.5427
10.0.14393.5427
Microsoft Windows 10=1607
10.0.14393.5427
Microsoft Windows Server 2016<10.0.14393.5427
10.0.14393.5427
Microsoft Windows 10=1607
10.0.14393.5427
Microsoft Windows 10<10.0.10240.19507
10.0.10240.19507
Microsoft Windows 10<10.0.10240.19507
10.0.10240.19507
Microsoft Windows 11=22H2
10.0.22621.674
Microsoft Windows 10=21H2
10.0.19044.2130
Microsoft Windows 11=22H2
10.0.22621.674
Microsoft Windows 10=21H2
10.0.19044.2130
Microsoft Windows 10=20H2
10.0.19042.2130
Microsoft Windows 11=21H2
10.0.22000.1098
Microsoft Windows 10=21H2
10.0.19044.2130
Microsoft Windows 10=20H2
10.0.19042.2130
Microsoft Windows 11=21H2
10.0.22000.1098
Microsoft Windows Server 2022<10.0.20348.1129
10.0.20348.1129
Microsoft Windows 10=21H1
10.0.19043.2130
Microsoft Windows 10=21H1
10.0.19043.2130
Microsoft Windows Server 2022<10.0.20348.1129
10.0.20348.1129
Microsoft Windows Server 2019<10.0.17763.3532
10.0.17763.3532
Microsoft Windows Server 2019<10.0.17763.3532
10.0.17763.3532
Microsoft Windows 10=21H1
10.0.19043.2130
Microsoft Windows 10=1809
10.0.17763.3532
Microsoft Windows 10=1809
10.0.17763.3532
Microsoft Windows 10=1809
10.0.17763.3532

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.23920Patch KB5018478
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.20625Patch KB5018476
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.1.7601.26174Patch KB5018479
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.0.6003.21721Patch KB5018446
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.20625Patch KB5018474
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.5427Patch KB5018411
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.10240.19507Patch KB5018425
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22621.674Patch KB5018427
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.2130Patch KB5018410
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19042.2130Patch KB5018410
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22000.1098Patch KB5018418
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.1129Patch KB5018421
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19043.2130Patch KB5018410
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.3532Patch KB5018419

Event History

Oct 11, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverity
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2022-41081?

CVE-2022-41081 is rated as critical, allowing for remote code execution.

2

How do I fix CVE-2022-41081?

To fix CVE-2022-41081, install the appropriate patches provided by Microsoft for the affected Windows versions.

3

What products are affected by CVE-2022-41081?

CVE-2022-41081 affects various versions of Microsoft Windows including Windows 10, Windows 11, and several Windows Server editions.

4

Can CVE-2022-41081 be exploited without authentication?

Yes, CVE-2022-41081 can be exploited remotely without requiring authentication.

5

Is there a workaround for CVE-2022-41081?

There are no documented workarounds for CVE-2022-41081, making patching essential.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203