Web-server crash via oversized session cookie
Published Aug 5, 2021 · Updated Aug 4, 2024
Stack overflow in checkLoginUser in TOTOLINK A720R firmware 4.1.5cu.470_B20200911 allows remote attackers to crash the web server. The ws_get_cookie routine locates SESSION_ID with strstr and copies all data after the equals sign into a 64-byte stack buffer with strcpy, without a length check. An unauthenticated crafted HTTP Cookie header is sufficient; the demonstrated consequence is a web-server crash on the router.
Summary
What happened
Stack overflow in checkLoginUser in TOTOLINK A720R firmware 4.1.5cu.470_B20200911 allows remote attackers to crash the web server. The ws_get_cookie routine locates SESSION_ID with strstr and copies all data after the equals sign into a 64-byte stack buffer with strcpy, without a length check. An unauthenticated crafted HTTP Cookie header is sufficient; the demonstrated consequence is a web-server crash on the router.
The record
- CVE
- CVE-2021-35325
- Published
- Aug 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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.
Public exploit references
- A720R SESSION_ID overflow 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