CVE-2024-30080: Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability

Published Jun 11, 2024
·
Updated

Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability

Affected Software

52 affected componentsFixes available
Microsoft Windows 10 1507<10.0.10240.20680
Microsoft Windows 10 1607<10.0.14393.7070
Microsoft Windows 10 1809<10.0.17763.5936
Microsoft Windows 10 21h1<10.0.19043.4529
Microsoft Windows 11 21h2<10.0.22000.3019
Microsoft Windows 11 22h2<10.0.22621.3737
Microsoft Windows 11 23h2<10.0.22631.3737
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<10.0.17763.5936
Microsoft Windows Server 2022<10.0.20348.2522
Microsoft Windows Server 2022 23h2<10.0.25398.950
Microsoft Windows Server 2012<6.2.9200.24919
6.2.9200.24919
Microsoft Windows Server 2008<6.0.6003.22720
6.0.6003.22720
Microsoft Windows Server 2012 R2<6.3.9600.22023
6.3.9600.22023
Microsoft Windows Server 2008 R2<6.1.7601.27170
6.1.7601.27170
Microsoft Windows Server 2012<6.2.9200.24919
6.2.9200.24919
Microsoft Windows Server 2008<6.0.6003.22720
6.0.6003.22720
Microsoft Windows Server 2012 R2<6.3.9600.22023
6.3.9600.22023
Microsoft Windows Server 2008 R2<6.1.7601.27170
6.1.7601.27170
Microsoft Windows Server 2008<6.0.6003.22720
6.0.6003.22720
Microsoft Windows Server 2016<10.0.14393.7070
10.0.14393.7070
Microsoft Windows Server 2016<10.0.14393.7070
10.0.14393.7070
Microsoft Windows Server 2008<6.0.6003.22720
6.0.6003.22720
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.950
10.0.25398.950
Microsoft Windows 10=1607
10.0.14393.7070
Microsoft Windows 10<10.0.10240.20680
10.0.10240.20680
Microsoft Windows 10=1607
10.0.14393.7070
Microsoft Windows 10=22H2
10.0.19045.4529
Microsoft Windows 10=22H2
10.0.19045.4529
Microsoft Windows 11=23H2
10.0.22631.3737
Microsoft Windows 11=23H2
10.0.22631.3737
Microsoft Windows 10<10.0.10240.20680
10.0.10240.20680
Microsoft Windows 10=22H2
10.0.19045.4529
Microsoft Windows 11=22H2
10.0.22621.3737
Microsoft Windows 11=22H2
10.0.22621.3737
Microsoft Windows 10=21H2
10.0.19044.4529
Microsoft Windows 10=21H2
10.0.19044.4529
Microsoft Windows 11=21H2
10.0.22000.3019
Microsoft Windows Server 2022<10.0.20348.2527, <10.0.20348.2522
10.0.20348.252710.0.20348.2522
Microsoft Windows 10=21H2
10.0.19044.4529
Microsoft Windows 11=21H2
10.0.22000.3019
Microsoft Windows Server 2019<10.0.17763.5936
10.0.17763.5936
Microsoft Windows Server 2022<10.0.20348.2527, <10.0.20348.2522
10.0.20348.252710.0.20348.2522
Microsoft Windows Server 2019<10.0.17763.5936
10.0.17763.5936
Microsoft Windows 10=1809
10.0.17763.5936
Microsoft Windows 10=1809
10.0.17763.5936
Microsoft Windows 10=1809
10.0.17763.5936

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.24919Patch KB5039260
  2. Upgrade

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

    Fixed in 6.0.6003.22720Patch KB5039266
  3. Upgrade

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

    Fixed in 6.3.9600.22023Patch KB5039294
  4. Upgrade

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

    Fixed in 6.1.7601.27170Patch KB5039274
  5. Upgrade

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

    Fixed in 10.0.14393.7070Patch KB5039214
  6. Upgrade

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

    Fixed in 10.0.25398.950Patch KB5039236
  7. Upgrade

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

    Fixed in 10.0.10240.20680Patch KB5039225
  8. Upgrade

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

    Fixed in 10.0.19045.4529Patch KB5039211
  9. Upgrade

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

    Fixed in 10.0.22631.3737Patch KB5039212
  10. Upgrade

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

    Fixed in 10.0.22621.3737Patch KB5039212
  11. Upgrade

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

    Fixed in 10.0.19044.4529Patch KB5039211
  12. Upgrade

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

    Fixed in 10.0.22000.3019Patch KB5039213
  13. Upgrade

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

    Fixed in 10.0.20348.2527Fixed in 10.0.20348.2522Patch KB5039330
  14. Upgrade

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

    Fixed in 10.0.17763.5936Patch KB5039217

Event History

Jun 11, 2024
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
CVE Published
via MITRE·04:59 PM
Data Sourced
via MITRE·04:59 PM
DescriptionSeverity
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 12, 2024
News Published
via The Register·12:29 AM
News Published
via The Register·12:34 AM
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-2024-30080?

CVE-2024-30080 is classified as a remote code execution vulnerability that could allow attackers to execute arbitrary code on affected systems.

2

How do I fix CVE-2024-30080?

To fix CVE-2024-30080, apply the relevant security updates and patches provided by Microsoft for your specific version of Windows.

3

What versions of Windows are affected by CVE-2024-30080?

CVE-2024-30080 affects various versions of Windows, including Windows 10, Windows Server 2012 R2, and Windows Server 2016 among others.

4

Can CVE-2024-30080 be exploited without user interaction?

Yes, CVE-2024-30080 can potentially be exploited remotely without requiring user interaction, posing a significant risk.

5

What are the recommended mitigations for CVE-2024-30080?

In addition to applying the patches, ensure your system is configured with security best practices, such as enabling firewalls and intrusion detection.

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