Credential disclosure via exposed cookie contents
Published Jun 15, 2021 · Updated Aug 3, 2024
Credential disclosure in TP-Link TL-WPA4220 firmware 4.0.2 Build 20180308 Rel.37064 allows remote attackers to obtain login credentials. The management interface places both the username and password in an HTTP cookie instead of limiting the cookie to a non-credential session token. Exploitation requires access to an issued cookie; disclosure exposes reusable device-management credentials.
Summary
What happened
Credential disclosure in TP-Link TL-WPA4220 firmware 4.0.2 Build 20180308 Rel.37064 allows remote attackers to obtain login credentials. The management interface places both the username and password in an HTTP cookie instead of limiting the cookie to a non-credential session token. Exploitation requires access to an issued cookie; disclosure exposes reusable device-management credentials.
The record
- CVE
- CVE-2021-28857
- Published
- Jun 15, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Weakness, pattern, technique
Public exploit references
- TP-Link’s TL-WPA4220 V4.0 Cleartext Credentials in Cookieproof of concept · unverified
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