Unauthenticated web-interface crash via malformed Referer
Published Mar 25, 2020 · Updated Mar 5, 2026
Denial-of-service in TP-Link Archer C50 V3 before Build 200318 Rel. 62209 allows remote attackers to interrupt the web interface via crafted HTTP headers. The web interface mishandles an unexpected Referer header, causing the HTTP service on port 80 to crash and close. Any remote network client can trigger the condition without authentication; restoring access requires a router reboot, with availability impact only.
Summary
What happened
Denial-of-service in TP-Link Archer C50 V3 before Build 200318 Rel. 62209 allows remote attackers to interrupt the web interface via crafted HTTP headers. The web interface mishandles an unexpected Referer header, causing the HTTP service on port 80 to crash and close. Any remote network client can trigger the condition without authentication; restoring access requires a router reboot, with availability impact only.
The record
- CVE
- CVE-2020-9375
- Published
- Mar 25, 2020
- Updated
- Mar 5, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-772, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2020CVE publishedPublication date reported by the CVE source.
- Mar 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- thewhiteh4t CVE-2020-9375 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo