Cyber Resilience

CVE-2024-0354

Path Traversal in Unknown-O Download-Station ≤ 1.1.8

Published
10 January 2024
Modified
21 November 2024
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0080 53th percentile
Risk Priority 46 floored blend · peak EPSS

Summary

CVE-2024-0354 is a medium-severity Path Traversal: '../filedir' (CWE-24) vulnerability in Unknown-O Download-Station. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability, which was classified as critical, has been found in unknown-o download-station up to 1.1.8. This issue affects some unknown processing of the file index.php. The manipulation of the argument f leads to path traversal: '../filedir'. The attack may…

more

be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-250121 was assigned to this vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-8409Shared CWE-22, CWE-24
CVE-2023-20166Shared CWE-22, CWE-24
CVE-2025-43928Shared CWE-22, CWE-24
CVE-2024-3686Shared CWE-22, CWE-24
CVE-2026-28427Shared CWE-22, CWE-24
CVE-2024-37403Shared CWE-22, CWE-24
CVE-2024-6786Shared CWE-22, CWE-24
CVE-2023-1398Shared CWE-22, CWE-24
CVE-2025-30343Shared CWE-22, CWE-24
CVE-2024-23657Shared CWE-22, CWE-24

Affected Assets

unknown-o
download-station
≤ 1.1.8

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)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes '../' sequences in externally-supplied pathnames before they are resolved.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

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 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent ../ traversal.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

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.

prevents

Secure coding standards require neutralizing ../ sequences and canonicalizing paths before file operations.

finds

Security testing in development catches path-traversal flaws before release.

prevents

Secure SDLC mandates input validation and path canonicalization that directly block ../ traversal.

prevents

Application security requirements explicitly call for controls against path traversal in file-handling functions.

prevents

Secure architecture principles reduce attack surface but do not prescribe the specific coding fix.

mitigates

Information access restriction limits which files can be reached, mitigating impact of traversal.

References