What is the CVSS score of CVE-2024-30062?

CVE-2024-30062 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.0%.

Is there a patch available for CVE-2024-30062?

Yes, a patch is available for CVE-2024-30062. Update the affected software to the latest version immediately.

Windows Server 2012 CVE-2024-30062

HIGH

Use After Free (CWE-416)

2024-06-11 secure@microsoft.com

Use After Free Microsoft RCE Memory Corruption Windows Server 2012 Windows Server 2016 Windows Server 2019 Windows Server 2022

7.8

CVSS 3.1 · Vendor: microsoft

Severity by source

Vendor (microsoft) PRIMARY

7.8 HIGH

AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary rating from Vendor (microsoft) · only source for this CVE.

CVSS VectorVendor: microsoft

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jun 11, 2024 - 17:15 cve.org

HIGH 7.8

DescriptionCVE.org

Windows Standards-Based Storage Management Service Remote Code Execution Vulnerability

AnalysisAI

Windows Standards-Based Storage Management Service Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. This Use After Free vulnerability could allow attackers to access freed memory to execute arbitrary code or crash the application.

Technical ContextAI

This vulnerability is classified as Use After Free (CWE-416), which allows attackers to access freed memory to execute arbitrary code or crash the application. Windows Standards-Based Storage Management Service Remote Code Execution Vulnerability Affected products include: Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use smart pointers or garbage-collected languages. Set pointers to NULL after freeing. Enable memory sanitizers.