CVE-2024-0416
Csdeshang Dsmall ≤ 5.0.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LSummary
CVE-2024-0416 is a medium-severity Path Traversal: '../filedir' (CWE-24) vulnerability in Csdeshang Dsmall. Its CVSS base score is 5.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
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-16211
Vulnerability Data
A vulnerability, which was classified as critical, has been found in DeShang DSMall up to 5.0.3. Affected by this issue is some unknown functionality of the file application/home/controller/MemberAuth.php. The manipulation of the argument file_name leads to path traversal: '../filedir'. The…
more
attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-250436.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly neutralizes '../' sequences in externally-supplied pathnames before they are resolved.
Enforced access authorizations can limit the damage even when path traversal succeeds.
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 prevent ../ traversal.
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 coding standards require neutralizing ../ sequences and canonicalizing paths before file operations.
Security testing in development catches path-traversal flaws before release.
Secure SDLC mandates input validation and path canonicalization that directly block ../ traversal.
Application security requirements explicitly call for controls against path traversal in file-handling functions.
Secure architecture principles reduce attack surface but do not prescribe the specific coding fix.
Information access restriction limits which files can be reached, mitigating impact of traversal.