Account takeover via username cookie manipulation
Published Feb 14, 2022 · Updated Aug 4, 2024
Improper authentication in ZZCMS 8.2 allows remote attackers to access an existing user's account by altering the username cookie. The authentication flow accepts any password when the cookie-supplied username matches an existing account. No prior account or user interaction is required, and successful exploitation provides access as the selected existing user.
Summary
What happened
Improper authentication in ZZCMS 8.2 allows remote attackers to access an existing user's account by altering the username cookie. The authentication flow accepts any password when the cookie-supplied username matches an existing account. No prior account or user interaction is required, and successful exploitation provides access as the selected existing user.
The record
- CVE
- CVE-2021-45347
- Published
- Feb 14, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2022CVE 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
- Cookie username authentication-bypass proof of conceptproof 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