Credential cracking via exposed authentication cookie
Published Apr 27, 2020 · Updated Aug 4, 2024
Insufficiently protected credentials in Rukovoditel 2.5.2 allow attackers to recover usernames and brute-force password hashes from cookies. The application persists both values in a client-side cookie, using URL and Base64 encoding while relying on hashing that permits offline guessing. Exploitation requires access to a user cookie and exposes its username and password hash; no modification or service interruption is reported.
Summary
What happened
Insufficiently protected credentials in Rukovoditel 2.5.2 allow attackers to recover usernames and brute-force password hashes from cookies. The application persists both values in a client-side cookie, using URL and Base64 encoding while relying on hashing that permits offline guessing. Exploitation requires access to a user cookie and exposes its username and password hash; no modification or service interruption is reported.
The record
- CVE
- CVE-2020-11821
- Published
- Apr 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 27, 2020CVE 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
- Rukovoditel password hash in cookie disclosureproof 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