Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2015-3035 is a high-severity Path Traversal (CWE-22) vulnerability in Tp-Link Tl-Wr841N Firmware. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.3% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities 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-2015-3035 is a directory traversal vulnerability (CWE-22) affecting multiple TP-LINK router models, including the Archer C5 (v1.2) with firmware prior to 150317, Archer C7 (v2.0) prior to 150304, Archer C8 (v1.0) prior to 150316, Archer C9 (v1.0), TL-WDR3500/3600/4300 (v1.0) prior to 150302, TL-WR740N/741ND (v5.0) prior to 150312, and TL-WR841N/ND (v9.0/10.0) prior to 150310. The flaw resides in the handling of the login/ endpoint, where a path traversal sequence in PATH_INFO permits access to files outside the intended web root.
Unauthenticated remote attackers can exploit the issue over the network by supplying crafted requests containing dot-dot sequences, resulting in disclosure of arbitrary files stored on the device with high confidentiality impact and no requirement for authentication or user interaction.
Vendor firmware updates addressing the affected models are referenced in the TP-LINK download archives and public disclosures on Packet Storm and Full Disclosure lists; applying the listed firmware revisions (such as 150317 for Archer C5) eliminates the traversal vector. No details on in-the-wild exploitation are provided in the source references.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2015-3116
Vulnerability Data
Directory traversal vulnerability in TP-LINK Archer C5 (1.2) with firmware before 150317, C7 (2.0) with firmware before 150304, and C8 (1.0) with firmware before 150316, Archer C9 (1.0), TL-WDR3500 (1.0), TL-WDR3600 (1.0), and TL-WDR4300 (1.0) with firmware before 150302, TL-WR740N…
more
(5.0) and TL-WR741ND (5.0) with firmware before 150312, and TL-WR841N (9.0), TL-WR841N (10.0), TL-WR841ND (9.0), and TL-WR841ND (10.0) with firmware before 150310 allows remote attackers to read arbitrary files via a .. (dot dot) in the PATH_INFO to login/.
- CWE(s)
- KEV Date Added
- 25 March 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
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.
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.
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 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.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.