Security readout for executives and security teams
Plain-English summary
A flaw in Microsoft SQL Server Native Scoring could let a low-privileged, network-connected attacker run unauthorized code. Successful exploitation could compromise database confidentiality, integrity, and availability. No user interaction is required, making affected and reachable SQL Server systems a high patching priority.
Executive priority
Treat this as a high-priority patching issue for affected SQL Server systems. Accelerate remediation where database access crosses trust boundaries or low-privileged accounts are widely available. Current evidence does not establish active exploitation, so prioritize using confirmed exposure and asset criticality rather than assuming an ongoing campaign.
Technical view
CVE-2024-37335 is a network-reachable heap-based buffer overflow (CWE-122) in SQL Server Native Scoring. CVSS 3.1 rates it 8.8: low complexity, low privileges, no user interaction, unchanged scope, and high potential impact across confidentiality, integrity, and availability.
Likely exposure
Potentially exposed deployments include the listed SQL Server 2017, 2019, and 2022 GDR or CU branches, particularly where attackers can obtain low-privileged database access over a network. The supplied evidence does not identify required features, configurations, or exact vulnerable build ranges beyond the listed branches.
Exploitation context
The supplied record does not report active exploitation, and the CVE is not identified as being in CISA KEV. Its CVSS exploit-maturity value is unproven. Nevertheless, network access, low complexity, low required privileges, and no user interaction make exploitation plausible if a vulnerable deployment is reachable.
Researcher notes
The supplied data establishes CWE-122, CVSS 8.8, and affected SQL Server servicing branches, but provides little root-cause or prerequisite detail. It does not establish whether Native Scoring must be enabled or invoked, identify attack preconditions beyond low privileges and network access, or provide exact fixed-build information. Consult Microsoft’s advisory for authoritative build mapping.
Mitigation direction
- Review Microsoft’s CVE advisory and apply the applicable SQL Server security update.
- Prioritize network-reachable systems and servers accessible to untrusted or broadly provisioned accounts.
- Restrict SQL Server network access and enforce least privilege while remediation is pending.
- Check vendor guidance before applying compensating controls not documented in the supplied sources.
Validation and detection
- Inventory SQL Server 2017, 2019, and 2022 instances, including GDR and CU servicing branches.
- Compare each installed build and servicing branch with Microsoft’s CVE advisory.
- Confirm applicable security updates installed successfully and required restarts completed.
- Review exposure paths and identify accounts capable of reaching affected SQL Server instances.
- Monitor vendor guidance and CVE records for revised affected-build or exploitation information.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-37335 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft SQL Server Native Scoring Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.