Security Resilience

CVE-2023-36433

Microsoft Dynamics 365 9.0 – 9.0.49.04

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

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-36433 is a medium-severity XPath Injection (CWE-643) vulnerability in Microsoft Dynamics 365. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); 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)

A05:2025 Injection

EU & UK References

Vulnerability Data

Microsoft Dynamics 365 (On-Premises) Information Disclosure Vulnerability

CWE(s)
CWE-643NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
attack.mitre.org →
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
attack.mitre.org →
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
attack.mitre.org →
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
attack.mitre.org →
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
attack.mitre.org →
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-24922Same product: Microsoft Dynamics 365
CVE-2023-36429Same product: Microsoft Dynamics 365
CVE-2024-21393Same product: Microsoft Dynamics 365
CVE-2024-43476Same product: Microsoft Dynamics 365
CVE-2023-21570Same product: Microsoft Dynamics 365
CVE-2023-36030Same product: Microsoft Dynamics 365
CVE-2023-36020Same product: Microsoft Dynamics 365
CVE-2023-35335Same product: Microsoft Dynamics 365
CVE-2023-21807Same product: Microsoft Dynamics 365
CVE-2024-21327Same product: Microsoft Dynamics 365

Affected Assets

microsoft
dynamics 365
9.0 — 9.0.49.04 · 9.1 — 9.1.21.05

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.4
  • V1.2.7
  • V2.2.1
  • V4.3.1

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.PS-06 partial match
blocks

Secure SDLC practices directly require input neutralization and query parameterization that prevent XPath injection.

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.

A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (code scan, penetration tests) and developer training that reach XPath injection as one of many injection flaws, but leaves a bounded remainder (e.g. incomplete rigour in outsourced development per 8.30, inconsistent application across all languages/projects, or post-SDLC changes)

A.8.26 Application security requirements partial match
blocks

Application security requirements explicitly call for defenses against injection flaws including XPath injection.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates security-by-design principles (including input distrust, data validation/sanitization, least privilege, and secure design reviews against attack patterns) that reach a slice of XPath injection prevention when applied to the relevant layer, but leaves most instances (implementation bugs in query construction) to other controls such as A.8.28 secure coding or A.8.29 testing.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper neutralization of untrusted input in XPath expressions.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development catches XPath injection vulnerabilities before release.

A.8.8 Management of technical vulnerabilities partial match
finds

Vulnerability management processes identify and remediate XPath injection flaws discovered post-deployment.

References