CVE-2023-0046
Daloradius ≤ 2023-01-04
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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-0046 is a high-severity Improper Restriction of Names for Files and Other Resources (CWE-641) vulnerability in Daloradius Daloradius. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-12149
Vulnerability Data
Improper Restriction of Names for Files and Other Resources in GitHub repository lirantal/daloradius prior to master-branch.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
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 sanitization to restrict resource names derived from untrusted data.
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 life cycle mandates input validation and safe resource naming practices that directly prevent CWE-641.
Application security requirements include rules for handling untrusted input when constructing file or resource names.
A.8.27 mandates security-by-design principles (least privilege, distrust external input, fail securely, security-oriented design reviews) that reach improper name construction for some file/resource cases but leave a bounded remainder (e.g. custom business logic for name sanitization or legacy components) unaddressed by the engineering principles alone.
Secure coding standards explicitly require validation and sanitization of filenames derived from external input.
Security testing can detect improper filename handling but does not itself prevent the weakness.