CVE-2022-34718: Windows TCP/IP Remote Code Execution Vulnerability

Published Sep 13, 2022
·
Updated

Windows TCP/IP Remote Code Execution Vulnerability

Affected Software

58 affected componentsFixes available
Microsoft Windows 10=20H2
Patch 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 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 2022
Microsoft Windows Server 2012<6.2.9200.23865
6.2.9200.23865
Microsoft Windows Server 2008 R2<6.1.7601.26115
6.1.7601.26115
Microsoft Windows Server 2012 R2<6.3.9600.20571
6.3.9600.20571
Microsoft Windows Server 2008<6.0.6003.21666
6.0.6003.21666
Microsoft Windows Server 2012<6.2.9200.23865
6.2.9200.23865
Microsoft Windows Server 2008<6.0.6003.21666
6.0.6003.21666
Microsoft Windows Server 2008 R2<6.1.7601.26115
6.1.7601.26115
Microsoft Windows Server 2008<6.0.6003.21666
6.0.6003.21666
Microsoft Windows Server 2012 R2<6.3.9600.20571
6.3.9600.20571
Microsoft Windows Server 2008<6.0.6003.21666
6.0.6003.21666
Microsoft Windows RT 8.1<6.3.9600.20571
6.3.9600.20571
Microsoft Windows 7<6.1.7601.26115
6.1.7601.26115
Microsoft Windows Server 2016<10.0.14393.5356
10.0.14393.5356
Microsoft Windows 8.1<6.3.9600.20571
6.3.9600.20571
Microsoft Windows 10=1607, >=10.0.14393<10.0.14393.5356
10.0.14393.5356
Microsoft Windows Server 2016<10.0.14393.5356
10.0.14393.5356
Microsoft Windows 7<6.1.7601.26115
6.1.7601.26115
Microsoft Windows 10=1607, >=10.0.14393<10.0.14393.5356
10.0.14393.5356
Microsoft Windows 8.1<6.3.9600.20571
6.3.9600.20571
Microsoft Windows 10=21H2, >=10.0.19044<10.0.19044.2006
10.0.19044.2006
Microsoft Windows 10=21H2, >=10.0.19044<10.0.19044.2006
10.0.19044.2006
Microsoft Windows 11=21H2, >=10.0.22000<10.0.22000.978
10.0.22000.978
Microsoft Windows 10=20H2, >=10.0.19042<10.0.19042.2006
10.0.19042.2006
Microsoft Windows 10=21H2, >=10.0.19044<10.0.19044.2006
10.0.19044.2006
Microsoft Windows 10<10.0.10240.19444
10.0.10240.19444
Microsoft Windows 10<10.0.10240.19444
10.0.10240.19444
Microsoft Windows 10=20H2, >=10.0.19042<10.0.19042.2006
10.0.19042.2006
Microsoft Windows 11=21H2, >=10.0.22000<10.0.22000.978
10.0.22000.978
Microsoft Windows Server 2022<10.0.20348.1006, <10.0.20348.916
10.0.20348.100610.0.20348.916
Microsoft Windows Server 2022<10.0.20348.1006, <10.0.20348.916
10.0.20348.100610.0.20348.916
Microsoft Windows 10=21H1, >=10.0.19043<10.0.19043.2006
10.0.19043.2006
Microsoft Windows 10=21H1, >=10.0.19043<10.0.19043.2006
10.0.19043.2006
Microsoft Windows 10=21H1, >=10.0.19043<10.0.19043.2006
10.0.19043.2006
Microsoft Windows 10=1809, >=10.0.17763<10.0.17763.3406
10.0.17763.3406
Microsoft Windows Server 2019<10.0.17763.3406
10.0.17763.3406
Microsoft Windows Server 2019<10.0.17763.3406
10.0.17763.3406
Microsoft Windows 10=1809, >=10.0.17763<10.0.17763.3406
10.0.17763.3406
Microsoft Windows 10=1809, >=10.0.17763<10.0.17763.3406
10.0.17763.3406

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.23865Patch KB5017377
  2. Upgrade

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

    Fixed in 6.3.9600.20571Patch KB5017365
  3. Upgrade

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

    Fixed in 6.1.7601.26115Patch KB5017373
  4. Upgrade

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

    Fixed in 6.0.6003.21666Patch KB5017371
  5. Upgrade

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

    Fixed in 6.3.9600.20571Patch KB5017367
  6. Upgrade

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

    Fixed in 10.0.14393.5356Patch KB5017305
  7. Upgrade

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

    Fixed in 10.0.19044.2006Patch KB5017308
  8. Upgrade

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

    Fixed in 10.0.22000.978Patch KB5017328
  9. Upgrade

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

    Fixed in 10.0.10240.19444Patch KB5017327
  10. Upgrade

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

    Fixed in 10.0.19042.2006Patch KB5017308
  11. Upgrade

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

    Fixed in 10.0.20348.1006Fixed in 10.0.20348.916Patch KB5017392
  12. Upgrade

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

    Fixed in 10.0.19043.2006Patch KB5017308
  13. Upgrade

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

    Fixed in 10.0.17763.3406Patch KB5017315

Event History

Sep 13, 2022
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·06:41 PM
Data Sourced
via MITRE·06:41 PM
DescriptionSeverity
Data Sourced
via NVD·07:15 PM
DescriptionSeverityAffected Software
Oct 3, 2022
Exploit Published
via GitHub·11:39 AM

Frequently Asked Questions

1

What is the severity of CVE-2022-34718?

CVE-2022-34718 is rated as critical, allowing for remote code execution on affected systems.

2

How do I fix CVE-2022-34718?

To fix CVE-2022-34718, apply the relevant security patches provided by Microsoft for your version of Windows.

3

Which versions of Windows are affected by CVE-2022-34718?

CVE-2022-34718 affects various versions of Windows including Windows 10, Windows 11, Windows Server 2008 R2, and Windows Server 2016.

4

What types of attacks are possible due to CVE-2022-34718?

CVE-2022-34718 can allow an attacker to execute arbitrary code on the target system if exploited.

5

Is there a workaround for CVE-2022-34718?

Currently, the recommended action is to apply the security updates, as there is no official workaround for CVE-2022-34718.

Company

Resources

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