Cyber Resilience

CVE-2024-6786

Path Traversal in Moxa Mxview One ≤ 1.4.1

Published
21 September 2024
Modified
30 September 2024
Patch / advisory
CVSS Score v4 6.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0055 43th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2024-6786 is a medium-severity Path Traversal: '../filedir' (CWE-24) vulnerability in Moxa Mxview One. Its CVSS base score is 6.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 43th percentile by exploit likelihood (below the median); 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

The vulnerability allows an attacker to craft MQTT messages that include relative path traversal sequences, enabling them to read arbitrary files on the system. This could lead to the disclosure of sensitive information, such as configuration files and JWT signing…

more

secrets.

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-2023-34216Same vendor: Moxa
CVE-2023-34217Same vendor: Moxa
CVE-2024-8409Shared CWE-22, CWE-24
CVE-2023-20166Shared CWE-22, CWE-24
CVE-2025-43928Shared CWE-22, CWE-24
CVE-2024-0354Shared 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-2023-1398Shared CWE-22, CWE-24

Affected Assets

moxa
mxview one
≤ 1.4.1

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