CVE-2021-41451: A misconfiguration in HTTP/1.0 and HTTP/1.1 of the web interface in TP-Link AX10v1 before V1_211117 allows...
A misconfiguration in HTTP/1.0 and HTTP/1.1 of the web interface in TP-Link AX10v1 before V1_211117 allows a remote unauthenticated attacker to send a specially crafted HTTP request and receive a misconfigured HTTP/0.9 response, potentially leading into a cache poisoning attack.
Security readout for executives and security teams
Plain-English summary
CVE-2021-41451 affects TP-Link Archer AX10 v1 firmware before V1_211117. The router web interface can mishandle specially crafted HTTP requests and return an unexpected HTTP/0.9 response. The published record says this could support cache poisoning. No CVSS score or confirmed exploitation is provided in the supplied sources.
Executive priority
Prioritize inventory and firmware verification for Archer AX10 v1 routers. Business urgency is evidence-limited: the flaw is remotely reachable and unauthenticated, but the sources do not provide severity scoring or confirmed exploitation.
Technical view
The issue is described as an HTTP/1.0 and HTTP/1.1 web-interface misconfiguration on TP-Link AX10v1 before V1_211117. A remote unauthenticated requester may trigger a misconfigured HTTP/0.9 response. The source record frames the consequence as potential cache poisoning, but does not provide protocol details, CVSS metrics, CWE mapping, or exploit telemetry.
Likely exposure
Exposure is limited to TP-Link Archer AX10 v1 devices running firmware before V1_211117, especially if the web interface is reachable from untrusted networks. The supplied data does not identify other TP-Link models, cloud services, or downstream products as affected.
Exploitation context
The CVE record supports remote unauthenticated reachability and potential cache poisoning. It does not cite public exploitation, weaponized tooling, or CISA KEV listing. Treat exploitation status as unconfirmed based on the supplied sources.
Researcher notes
The public record is sparse. Key missing details include cache interaction requirements, affected deployment topology, precise fixed firmware behavior, CVSS vector, and CWE classification. Avoid extending scope beyond AX10v1 before V1_211117 without vendor evidence.
Mitigation direction
Identify Archer AX10 v1 devices and record firmware versions.
Update affected devices to V1_211117 or later vendor firmware, if available.
Restrict management web-interface access to trusted administrative networks.
Disable external exposure of the router management interface where possible.
Check TP-Link firmware guidance before applying production changes.
Validation and detection
Confirm device model is Archer AX10 v1, not another hardware revision.
Compare installed firmware against V1_211117.
Verify management interface is not reachable from the public internet.
Review router logs for unusual web-interface access attempts.
Document exceptions where firmware cannot be upgraded immediately.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-41451 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
2Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 17, 2021, 14:32 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.