CVE-2023-40623
Sap Businessobjects 420 … 430
Raw vector
CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-40623 is a medium-severity Insecure Operation on Windows Junction / Mount Point (CWE-1386) vulnerability in Sap Businessobjects. Its CVSS base score is 6.2 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-45179
Vulnerability Data
SAP BusinessObjects Suite Installer - version 420, 430, allows an attacker within the network to create a directory under temporary directory and link it to a directory with operating system files. On successful exploitation the attacker can delete all the…
more
operating system files causing a limited impact on integrity and completely compromising the availability of the system.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.3
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.
Secure SDLC practices directly prevent improper junction/mount-point handling during design and coding.
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.
Secure development lifecycle can mandate junction/mount-point validation during design and coding.
Application security requirements can explicitly require protection against Windows reparse-point attacks.
A.8.27 mandates security-by-design, defence-in-depth, least-privilege, distrust-external-input and hardening principles plus design reviews that can catch and block insecure junction/mount-point handling in the architecture and code, but leaves a bounded remainder (e.g. third-party libraries, runtime config, or post-deployment changes) where the flaw can still be introduced and exploited.
Secure coding standards directly address safe file/directory handling to prevent insecure junction operations.