Security readout for executives and security teams
Plain-English summary
This high-severity flaw could let a low-privileged, network-connected attacker execute code against vulnerable Microsoft Dynamics 365 Business Central deployments. Successful exploitation could expose or alter business data and disrupt service. The supplied sources identify affected release families but provide limited technical detail about the vulnerable component.
Executive priority
Prioritize remediation promptly because exploitation could compromise sensitive business data and operations without user interaction. Internet-facing or broadly accessible deployments deserve accelerated handling. Confirm ownership, patch status, and any remediation exceptions.
Technical view
CVE-2024-35249 is classified as CWE-502, deserialization of untrusted data. Its CVSS 3.1 score is 8.8: network-accessible, low complexity, low privileges required, no user interaction, and potentially high confidentiality, integrity, and availability impact. Scope remains unchanged.
Likely exposure
Exposure is most likely where Business Central 2023 Release Wave 1 version 22.0.0, 2023 Release Wave 2 version 23.0.0, or 2024 Release Wave 1 version 24.0 is deployed and reachable by low-privileged users over a network.
Exploitation context
The CVSS vector indicates an attacker needs low-level privileges but no victim interaction. The supplied bundle says this CVE is not in CISA KEV, and no cited source establishes active exploitation. Exploit maturity is recorded as unproven.
Researcher notes
The public bundle identifies CWE-502 and the CVSS conditions but does not describe the deserialization entry point, affected component, protocol, or precise attack preconditions. Treat those details as unknown and consult Microsoft’s advisory before designing safe validation procedures.
Mitigation direction
- Inventory Business Central deployments and identify the listed affected releases and versions.
- Review Microsoft’s CVE advisory for the applicable security update and installation requirements.
- Apply the vendor-provided update using normal change control and backup procedures.
- Restrict unnecessary network access and low-privileged accounts until remediation is confirmed.
Validation and detection
- Confirm deployed Business Central versions through authoritative asset and configuration records.
- Verify Microsoft’s applicable security update is installed on every affected instance.
- Test application availability and critical business workflows after updating.
- Review authentication and application logs for unusual low-privileged activity around exposed instances.
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-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-35249 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 Dynamics 365 Business Central 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.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.