CVE-2023-21823: Windows Graphics Component Remote Code Execution Vulnerability

Published Feb 14, 2023
·
Updated

Microsoft Windows Graphic Component contains an unspecified vulnerability that allows for privilege escalation.

Other sources

Windows Graphics Component Remote Code Execution Vulnerability

Affected Software

68 affected componentsFixes available
Microsoft Windows 10 1507<10.0.10240.19747
Microsoft Windows 10 1507<10.0.10240.19747
Microsoft Windows 10 1607<10.0.14393.5717
Microsoft Windows 10 1607<10.0.14393.5717
Microsoft Windows 10 1809<10.0.17763.4010
Microsoft Windows 10 1809<10.0.17763.4010
Microsoft Windows 10 1809<10.0.17763.4010
Microsoft Windows 10 20h2<10.0.19042.2604
Microsoft Windows 10 20h2<10.0.19042.2604
Microsoft Windows 10 20h2<10.0.19042.2604
Microsoft Windows 10 21h2<10.0.19044.2604
Microsoft Windows 10 21h2<10.0.19044.2604
Microsoft Windows 10 21h2<10.0.19044.2604
Microsoft Windows 10 22h2<10.0.19045.2604
Microsoft Windows 10 22h2<10.0.19045.2604
Microsoft Windows 10 22h2<10.0.19045.2604
Microsoft Windows 11 21h2<10.0.22000.1574
Microsoft Windows 11 21h2<10.0.22000.1574
Microsoft Windows 11 22h2<10.0.22621.1265
Microsoft Windows 11 22h2<10.0.22621.1265
Microsoft Windows Server 2008=sp2
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 10=20H2
Microsoft Windows
Microsoft Windows Server 2012<6.2.9200.24116
6.2.9200.24116
Microsoft Windows Server 2012<6.2.9200.24116
6.2.9200.24116
Microsoft Windows Server 2008<6.0.6003.21915
6.0.6003.21915
Microsoft Windows Server 2012 R2<6.3.9600.20821
6.3.9600.20821
Microsoft Windows Server 2008 R2<6.1.7601.26366
6.1.7601.26366
Microsoft Windows Server 2008 R2<6.1.7601.26366
6.1.7601.26366
Microsoft Windows Server 2012 R2<6.3.9600.20821
6.3.9600.20821
Microsoft Windows Server 2008<6.0.6003.21915
6.0.6003.21915
Microsoft Windows Server 2008<6.0.6003.21915
6.0.6003.21915
Microsoft Windows Server 2008<6.0.6003.21915
6.0.6003.21915
Microsoft Windows Server 2016<10.0.14393.5717
10.0.14393.5717
Microsoft Windows Server 2016<10.0.14393.5717
10.0.14393.5717
Microsoft Windows 10=1607
10.0.14393.5717
Microsoft Windows 10<10.0.10240.19747
10.0.10240.19747
Microsoft Windows 10=22H2
10.0.19045.2604
Microsoft Windows 10=1607
10.0.14393.5717
Microsoft Windows 10<10.0.10240.19747
10.0.10240.19747
Microsoft Windows 10=22H2
10.0.19045.2604
Microsoft Windows 10=22H2
10.0.19045.2604
Microsoft Windows 10=21H2
10.0.19044.2604
Microsoft Windows 11=22H2
10.0.22621.1265
Microsoft Windows 10=21H2
10.0.19044.2604
Microsoft Windows 10=21H2
10.0.19044.2604
Microsoft Windows 11=22H2
10.0.22621.1265
Microsoft Windows 11=21H2
10.0.22621.1574
Microsoft Windows Server 2022<10.0.20348.1547, <10.0.20348.1540
10.0.20348.154710.0.20348.1540
Microsoft Windows 10=20H2
10.0.19042.2604
Microsoft Windows 11=21H2
10.0.22621.1574
Microsoft Windows 10=20H2
10.0.19042.2604
Microsoft Windows Server 2019<10.0.17763.4010
10.0.17763.4010
Microsoft Windows Server 2022<10.0.20348.1547, <10.0.20348.1540
10.0.20348.154710.0.20348.1540
Microsoft Windows 10=1809
10.0.17763.4010
Microsoft Windows Server 2019<10.0.17763.4010
10.0.17763.4010
Microsoft Office for Universal<16.0.14326.21330
16.0.14326.21330
Microsoft Windows 10=1809
10.0.17763.4010
Microsoft Office for iOS<2.70.23021003
2.70.23021003
Microsoft Office for Android<16.0.16130.20156
16.0.16130.20156
Microsoft Windows 10=1809
10.0.17763.4010

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.24116Patch KB5022895
  2. Upgrade

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

    Fixed in 6.0.6003.21915Patch KB5022893
  3. Upgrade

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

    Fixed in 6.3.9600.20821Patch KB5022894
  4. Upgrade

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

    Fixed in 6.1.7601.26366Patch KB5022874
  5. Upgrade

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

    Fixed in 10.0.14393.5717Patch KB5022838
  6. Upgrade

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

    Fixed in 10.0.10240.19747Patch KB5022858
  7. Upgrade

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

    Fixed in 10.0.19045.2604Patch KB5022834
  8. Upgrade

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

    Fixed in 10.0.19044.2604Patch KB5022834
  9. Upgrade

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

    Fixed in 10.0.22621.1265Patch KB5022845
  10. Upgrade

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

    Fixed in 10.0.22621.1574Patch KB5022836
  11. Upgrade

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

    Fixed in 10.0.20348.1547Fixed in 10.0.20348.1540Patch KB5022921
  12. Upgrade

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

    Fixed in 10.0.19042.2604Patch KB5022834
  13. Upgrade

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

    Fixed in 10.0.17763.4010Patch KB5022840
  14. Upgrade

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

    Fixed in 16.0.14326.21330
  15. Upgrade

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

    Fixed in 2.70.23021003
  16. Upgrade

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

    Fixed in 16.0.16130.20156

Event History

Feb 14, 2023
CVE Published
via CISA·12:00 AM
Known Exploited
via CISA·12: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
DescriptionWeakness
Updated
via Microsoft·08:00 AM
DescriptionSeverity
CVE Published
via MITRE·08:09 PM
Data Sourced
via MITRE·08:09 PM
DescriptionSeverity
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected 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-2023-21823?

CVE-2023-21823 has a high severity rating due to its potential for privilege escalation.

2

How do I fix CVE-2023-21823?

To fix CVE-2023-21823, apply the latest security updates provided by Microsoft for the affected products.

3

Which Microsoft products are affected by CVE-2023-21823?

CVE-2023-21823 affects multiple Microsoft products, including Windows Server 2016, Windows 10, and Windows 11.

4

Can CVE-2023-21823 be exploited remotely?

Yes, CVE-2023-21823 can potentially be exploited remotely, allowing an attacker to execute arbitrary code.

5

What type of vulnerability is CVE-2023-21823?

CVE-2023-21823 is classified as a remote code execution vulnerability in the Windows Graphics Component.

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