CVE-2024-37337 | Microsoft SQL Server Native Scoring Information Disclosure Vulnerability

Microsoft SQL Server Native Scoring Information Disclosure Vulnerability

Published: 2024-09-10 Last update: 2024-09-23 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-37337 is rated Moderate Risk (54.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.70%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-37337

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 1.29% 1.70% +0.40%
2 2026-01-30 1.41% 1.29% -0.12%
3 2026-01-17 — 1.41% —

Full EPSS history (24 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-37337

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.8 4.2 [email protected]
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [email protected]

Weakness enumeration for CVE-2024-37337

Affected software / configurations for CVE-2024-37337

Vendor Product Version Raw CPE
microsoft sql_2016_azure_connect_feature_pack >= 13.0.7000.253, <= 13.0.7037.1 cpe:2.3:a:microsoft:sql_2016_azure_connect_feature_pack:*:*:*:*:*:*:*:*
microsoft sql_server_2016 >= 13.0.6300.2, < 13.0.6441.1 cpe:2.3:a:microsoft:sql_server_2016:*:*:*:*:*:*:x64:*
microsoft sql_server_2017 >= 14.0.1000.169, < 14.0.2060.1 cpe:2.3:a:microsoft:sql_server_2017:*:*:*:*:*:*:x64:*
microsoft sql_server_2017 >= 14.0.3006.16, < 14.0.3475.1 cpe:2.3:a:microsoft:sql_server_2017:*:*:*:*:*:*:x64:*
microsoft sql_server_2019 >= 15.0.2000.5, < 15.0.2120.1 cpe:2.3:a:microsoft:sql_server_2019:*:*:*:*:*:*:x64:*
microsoft sql_server_2019 >= 15.0.4003.23, < 15.0.4390.2 cpe:2.3:a:microsoft:sql_server_2019:*:*:*:*:*:*:x64:*
microsoft sql_server_2022 >= 16.0.1000.6, < 16.0.1125.1 cpe:2.3:a:microsoft:sql_server_2022:*:*:*:*:*:*:x64:*
microsoft sql_server_2022 >= 16.0.4003.1, < 16.0.4140.3 cpe:2.3:a:microsoft:sql_server_2022:*:*:*:*:*:*:x64:*

References for CVE-2024-37337

cvelogic Threat Intelligence