Cyber Resilience

CVE-2023-35621

Microsoft Dynamics 365 10.0.37 … 10.0.38

Published
12 December 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.023 82th percentile
Risk Priority 62 floored blend · peak EPSS

Summary

CVE-2023-35621 is a high-severity Improper Control of Interaction Frequency (CWE-799) vulnerability in Microsoft Dynamics 365. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked in the top 18% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Microsoft Dynamics 365 Finance and Operations Denial of Service Vulnerability

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1499.002 Service Exhaustion Flood Impact
Adversaries may target the different network services provided by systems to conduct a denial of service (DoS).
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
T1667 Email Bombing Impact
Adversaries may flood targeted email addresses with an overwhelming volume of messages.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
T1110.003 Password Spraying Credential Access
Adversaries may use a single or small list of commonly used passwords against many different accounts to attempt to acquire valid account credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38182Same product: Microsoft Dynamics 365
CVE-2023-21778Same product: Microsoft Dynamics 365
CVE-2023-36410Same product: Microsoft Dynamics 365
CVE-2023-21572Same product: Microsoft Dynamics 365
CVE-2024-21393Same product: Microsoft Dynamics 365
CVE-2024-21419Same product: Microsoft Dynamics 365
CVE-2023-21807Same product: Microsoft Dynamics 365
CVE-2023-21573Same product: Microsoft Dynamics 365
CVE-2023-36800Same product: Microsoft Dynamics 365
CVE-2023-24921Same product: Microsoft Dynamics 365

Affected Assets

microsoft
dynamics 365
10.0.37, 10.0.38, all versions

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-799

The control requires defining frequency, timing, and approval for security interactions, directly addressing uncontrolled interaction rates.

addresses: CWE-799

Allocation policies inherently restrict interaction frequency, reducing the impact of excessive requests.

addresses: CWE-799

Spam protection explicitly controls interaction frequency by detecting and acting on bulk unsolicited messages from external sources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.IR-01 partial match
prevents

Protecting networks from unauthorized usage can incorporate rate limiting to bound interaction frequency.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

Network security controls can enforce rate limiting and throttling at the perimeter.

prevents

Application security requirements explicitly include controls on interaction frequency and throttling.

prevents

Secure architecture principles recommend rate-limiting and resource-management mechanisms.

prevents

Secure coding practices can embed input-frequency and throttling checks in code.

degrades

Capacity management directly limits request rates and resource exhaustion that CWE-799 describes.

References