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

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

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

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

Sql 2016 Azure Connect Feature Pack CVE-2024-26186

HIGH

Use After Free (CWE-416)

2024-09-10 secure@microsoft.com

Use After Free Microsoft RCE Memory Corruption Sql 2016 Azure Connect Feature Pack Sql Server 2016 Sql Server 2017 Sql Server 2019 Sql Server 2022

8.8

CVSS 3.1 · Vendor: microsoft

Severity by source

Vendor (microsoft) PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/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:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Sep 10, 2024 - 17:15 cve.org

HIGH 8.8

DescriptionCVE.org

Microsoft SQL Server Native Scoring Remote Code Execution Vulnerability

AnalysisAI

Microsoft SQL Server Native Scoring Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, 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. Microsoft SQL Server Native Scoring Remote Code Execution Vulnerability Affected products include: Microsoft Sql 2016 Azure Connect Feature Pack, Microsoft Sql Server 2016, Microsoft Sql Server 2017, Microsoft Sql Server 2019, Microsoft Sql 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.