Cyber Resilience

CVE-2023-47464

Path Traversal in Gl-Inet Gl-Ax1800 Firmware 4.0.0 – 4.5.0

Public PoCPath Traversal
Published
30 November 2023
Modified
21 November 2024
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.23 98th percentile
Risk Priority 89 floored blend · peak EPSS

Summary

CVE-2023-47464 is a high-severity Path Traversal (CWE-22) vulnerability in Gl-Inet Gl-Ax1800 Firmware. 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 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2023-47464 is an insecure permissions vulnerability, tracked under CWE-22, that affects the upload API function in GL.iNet AX1800 firmware versions 4.0.0 through 4.4.x. The flaw permits path traversal or unauthorized file placement during upload operations, enabling remote code execution on the device.

An attacker with valid low-privileged credentials can reach the affected API over the network and supply crafted upload requests. Successful exploitation grants the ability to write arbitrary files, resulting in full compromise of confidentiality, integrity, and availability on the router.

Public disclosure is documented in the GL.iNet CVE repository, which details the arbitrary file creation vector through the upload endpoint and identifies the fixed release as version 4.5.0. The associated EPSS score has remained at 0.7010 with no indicated upward trajectory after publication.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Insecure Permissions vulnerability in GL.iNet AX1800 version 4.0.0 before 4.5.0 allows a remote attacker to execute arbitrary code via the upload API function.

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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-31477Same product: Gl-Inet Gl-Ax1800
CVE-2024-45262Same vendor: Gl-Inet
CVE-2023-46455Same vendor: Gl-Inet
CVE-2024-39226Same vendor: Gl-Inet
CVE-2025-21048Shared CWE-22
CVE-2026-23939Shared CWE-22
CVE-2024-7145Shared CWE-22
CVE-2023-42225Shared CWE-22
CVE-2024-33109Shared CWE-22
CVE-2023-35016Shared CWE-22

Affected Assets

gl-inet
gl-ax1800 firmware
4.0.0 — 4.5.0

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

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-22

Validates pathnames and filenames to prevent traversal outside intended directories.

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-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.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References