Cache poisoning via HTTP/0.9 downgrade
Published Dec 17, 2021 · Updated Jul 9, 2026
HTTP response confusion in the TP-Link Archer AX10 V1 web interface before V1_211117 allows remote attackers to expose intermediary caches to poisoning. The parser accepts GET or POST requests labeled HTTP/0.9 and answers with that obsolete version while retaining HTTP headers except Content-Length. No authentication is required; poisoning requires an intermediary cache that treats the protocol-confused response as cacheable content.
Summary
What happened
HTTP response confusion in the TP-Link Archer AX10 V1 web interface before V1_211117 allows remote attackers to expose intermediary caches to poisoning. The parser accepts GET or POST requests labeled HTTP/0.9 and answers with that obsolete version while retaining HTTP headers except Content-Length. No authentication is required; poisoning requires an intermediary cache that treats the protocol-confused response as cacheable content.
The record
- CVE
- CVE-2021-41451
- Published
- Dec 17, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-444
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 17, 2021CVE publishedPublication date reported by the CVE source.
- Jul 9, 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
- HTTP/0.9 downgrade request demonstrationproof 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