dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Apr 2022.
Tl Wr741nd FirmwareOperating system · Tp Link

CVE-2015-3035

HIGH · 7.5 CVSS v3.1 Published 2015-04-22
Fix available
A fix is available. Upgrade to 150302 / 150304 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 (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/.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A directory traversal vulnerability in TP-LINK Archer and TL-WR series routers allows remote attackers to read arbitrary files on the device by using '..' (dot dot) sequences in the PATH_INFO parameter to the login/ endpoint. This occurs due to insufficient input validation in the web interface.

MitigationApply the appropriate TP-LINK firmware update for the specific router model (C5, C7, C8, C9, WDR3500, WDR3600, WDR4300, WR740N, WR741ND, WR841N) to a version newer than the dates specified in the CVE description.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tl Wr741nd FirmwareOperating system
Affected:< 150312
Tl Wr841n FirmwareOperating system
Affected:< 150310
Tl Wr740n FirmwareOperating system
Affected:< 150312
Archer C5 FirmwareOperating system
Affected:< 150317
Tl Wdr3600 FirmwareOperating system
Affected:< 150302
Archer C7 FirmwareOperating system
Affected:< 150304
Tl Wr841nd FirmwareOperating system
Affected:< 150310
Archer C9 FirmwareOperating system
Affected:< 150302

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the TP-LINK router model
    Log into the router web interface and navigate to Status or System Settings page to view the device model, or inspect the physical device label
    Affected if The model is one of the following: Archer C5, Archer C7, Archer C9, TL-WR740N, TL-WR741ND, TL-WR841N, TL-WR841ND, TL-WDR3600
  2. Check the installed firmware version
    In the router web interface, go to Status or System Tools > Firmware Upgrade (or similar) to view the current firmware version/build date
    Affected if The firmware version is earlier than the threshold: WR741ND < 150312, WR841N < 150310, WR740N < 150312, Archer C5 < 150317, WDR3600 < 150302, Archer C7 < 150304, WR841ND < 150310, Archer C9 < 150302
  3. Determine if the router web interface is externally accessible
    Check router WAN/Internet-facing settings or test access to the web interface from an external network by attempting to reach the router's public IP on port 80/443
    Affected if The web interface is accessible from the WAN/Internet side (remote management enabled)
  4. Verify if the login endpoint accepts path traversal
    Send an HTTP GET request to http://[router-ip]/login/..%2f..%2f..%2f/etc/passwd or similar path traversal pattern targeting the login/ endpoint
    Affected if The request returns file contents from the device filesystem or a directory listing showing traversal succeeded

A user is affected if they have a TP-LINK router from the affected model list, running firmware older than the specified version thresholds, with the web interface exposed (especially externally).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 150302 / 150304 / 150310 or later
Fixed in 150302150304150310
Interim mitigation

Apply the appropriate TP-LINK firmware update for the specific router model (C5, C7, C8, C9, WDR3500, WDR3600, WDR4300, WR740N, WR741ND, WR841N) to a version newer than the dates specified in the CVE description.

Recommended fix High confidence

Device-specific firmware: TL-WR741ND/WR740N >= 150312, TL-WR841N/WR841ND >= 150310, Archer C5 >= 150317, Archer C7 >= 150304, Archer C9/TL-WDR3600 >= 150302

  1. 1. Identify the exact model number and current firmware version of your TP-LINK device
  2. 2. Visit the official TP-LINK support page at www.tp-link.com and navigate to the Downloads section for your specific model
  3. 3. Download the firmware version >= the minimum fixed version for your device: TL-WR741ND/WR740N: 150312, TL-WR841N/WR841ND: 150310, Archer C5: 150317, Archer C7: 150304, Archer C9/TL-WDR3600: 150302
  4. 4. Access the router's web management interface and navigate to the Firmware Upgrade or System Tools section
  5. 5. Upload the downloaded firmware file and wait for the upgrade process to complete (do not power off the device)
  6. 6. After reboot, verify the new firmware version in the router status page
  7. 7. Change administrator credentials as a precautionary measure after the upgrade
Caveat Firmware upgrades on older routers may reset configuration to defaults; backup current settings before upgrading and re-apply after

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tl Wr741nd Firmware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-3035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-3035 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data