CVE-2024-41376
Dzzoffice 2.02.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-41376 is a high-severity Path Traversal: 'dir\..\..\filename' (CWE-31) vulnerability in Dzzoffice Dzzoffice. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-39036
Vulnerability Data
dzzoffice 2.02.1 is vulnerable to Directory Traversal via user/space/about.php.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of path inputs, stopping the acceptance of backslash dot-dot sequences that escape the restricted directory.
Enforces authorization checks on file/resource access, blocking exploitation of a traversed path even if the malformed name is accepted.
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 require input validation and path sanitization that block this weakness.
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.
Security testing can discover traversal flaws but does not prevent them at the source.
Secure development lifecycle mandates input validation and path sanitization that directly blocks directory traversal sequences.
Application security requirements explicitly call for controls against path traversal and other injection flaws.
Secure architecture principles reduce the attack surface but do not prescribe the specific coding fix.
Secure coding standards require canonicalization and whitelist validation that eliminate CWE-31.