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

Published Nov 8, 2022
·
Updated

Windows Point-to-Point Tunneling Protocol Remote Code Execution Vulnerability

Affected Software

59 affected componentsFixes available
Microsoft Windows 10
Microsoft Windows 10=20h2
Microsoft Windows 10=21h1
Microsoft Windows 10=21h2
Microsoft Windows 10=22h2
Microsoft Windows 10=1607
Microsoft Windows 10=1809
Microsoft Windows 11
Microsoft Windows 11
Microsoft Windows 11=22h2
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows RT 8.1
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 2022
Microsoft Windows Server 2012 R2<6.3.9600.20671, <6.3.9600.20670
6.3.9600.206716.3.9600.20670
Microsoft Windows Server 2012<6.2.9200.23968
6.2.9200.23968
Microsoft Windows Server 2012 R2<6.3.9600.20671, <6.3.9600.20670
6.3.9600.206716.3.9600.20670
Microsoft Windows Server 2012<6.2.9200.23968
6.2.9200.23968
Microsoft Windows Server 2008 R2<6.1.7601.26221
6.1.7601.26221
Microsoft Windows 8.1 for 32-bit systems<6.3.9600.20671, <6.3.9600.20670
6.3.9600.206716.3.9600.20670
Microsoft Windows 8.1 for x64-based systems<6.3.9600.20671, <6.3.9600.20670
6.3.9600.206716.3.9600.20670
Microsoft Windows RT 8.1<6.3.9600.20670
6.3.9600.20670
Microsoft Windows Server 2008 R2<6.1.7601.26221
6.1.7601.26221
Microsoft Windows 7<6.1.7601.26221
6.1.7601.26221
Microsoft Windows 7<6.1.7601.26221
6.1.7601.26221
Microsoft Windows Server 2016<10.0.14393.5501
10.0.14393.5501
Microsoft Windows 10<10.0.10240.19567
10.0.10240.19567
Microsoft Windows 10=1607
10.0.14393.5501
Microsoft Windows 10=1607
10.0.14393.5501
Microsoft Windows Server 2016<10.0.14393.5501
10.0.14393.5501
Microsoft Windows 10<10.0.10240.19567
10.0.10240.19567
Microsoft Windows 10=22H2
10.0.19045.2251
Microsoft Windows 10=22H2
10.0.19045.2251
Microsoft Windows 11=22H2
10.0.22621.819
Microsoft Windows 10=22H2
10.0.19045.2251
Microsoft Windows 10=21H2
10.0.19044.2251
Microsoft Windows 11=22H2
10.0.22621.819
Microsoft Windows 11=21H2
10.0.22000.1219
Microsoft Windows 10=21H2
10.0.19044.2251
Microsoft Windows 10=21H2
10.0.19044.2251
Microsoft Windows 11=21H2
10.0.22000.1219
Microsoft Windows Server 2022<10.0.20348.1249, <10.0.20348.1251
10.0.20348.124910.0.20348.1251
Microsoft Windows 10=20H2
10.0.19042.2251
Microsoft Windows 10=20H2
10.0.19042.2251
Microsoft Windows 10=21H1
10.0.19043.2251
Microsoft Windows 10=21H1
10.0.19043.2251
Microsoft Windows 10=21H1
10.0.19043.2251
Microsoft Windows Server 2022<10.0.20348.1249, <10.0.20348.1251
10.0.20348.124910.0.20348.1251
Microsoft Windows Server 2019<10.0.17763.3650
10.0.17763.3650
Microsoft Windows Server 2019<10.0.17763.3650
10.0.17763.3650
Microsoft Windows 10=1809
10.0.17763.3650
Microsoft Windows 10=1809
10.0.17763.3650
Microsoft Windows 10=1809
10.0.17763.3650

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.23968Patch KB5020003
  2. Upgrade

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

    Fixed in 6.3.9600.20671Fixed in 6.3.9600.20670Patch KB5020010
  3. Upgrade

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

    Fixed in 6.1.7601.26221Patch KB5020013
  4. Upgrade

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

    Fixed in 6.3.9600.20670Patch KB5020010
  5. Upgrade

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

    Fixed in 10.0.14393.5501Patch KB5019964
  6. Upgrade

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

    Fixed in 10.0.10240.19567Patch KB5019970
  7. Upgrade

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

    Fixed in 10.0.19045.2251Patch KB5019959
  8. Upgrade

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

    Fixed in 10.0.22621.819Patch KB5019980
  9. Upgrade

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

    Fixed in 10.0.19044.2251Patch KB5019959
  10. Upgrade

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

    Fixed in 10.0.22000.1219Patch KB5019961
  11. Upgrade

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

    Fixed in 10.0.19042.2251Patch KB5019959
  12. Upgrade

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

    Fixed in 10.0.20348.1249Fixed in 10.0.20348.1251Patch KB5019080
  13. Upgrade

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

    Fixed in 10.0.19043.2251Patch KB5019959
  14. Upgrade

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

    Fixed in 10.0.17763.3650Patch KB5019966

Event History

Nov 8, 2022
CVE Published
via Microsoft·08:00 AM
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Description
Nov 9, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverity
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected 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-41039?

CVE-2022-41039 is classified as a critical vulnerability that allows remote code execution in Windows Point-to-Point Tunneling Protocol.

2

How do I fix CVE-2022-41039?

To fix CVE-2022-41039, ensure you apply the latest security updates from Microsoft that address this vulnerability.

3

What products are affected by CVE-2022-41039?

CVE-2022-41039 affects multiple Microsoft products including various versions of Windows 10, Windows 11, and Windows Server 2022.

4

Can CVE-2022-41039 be exploited remotely?

Yes, CVE-2022-41039 can be exploited remotely by an attacker to execute arbitrary code on affected systems.

5

What recommendations are there for mitigating the risk of CVE-2022-41039?

In addition to applying patches, it is recommended to limit exposure to the affected services and implement proper firewall rules.

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