Brute-force protection bypass via username case variants
Published Feb 11, 2020 · Updated Aug 4, 2024
Improper username canonicalization in MISP before 2.4.121 allows remote attackers to bypass brute-force login protection. Bruteforce::insert stored the submitted username unchanged, while isBlacklisted counted exact username matches, so case and whitespace variants created separate failure records. Repeated unauthenticated login attempts can therefore continue password guessing beyond the configured threshold, but the flaw does not itself disclose credentials or grant access.
Summary
What happened
Improper username canonicalization in MISP before 2.4.121 allows remote attackers to bypass brute-force login protection. Bruteforce::insert stored the submitted username unchanged, while isBlacklisted counted exact username matches, so case and whitespace variants created separate failure records. Repeated unauthenticated login attempts can therefore continue password guessing beyond the configured threshold, but the flaw does not itself disclose credentials or grant access.
The record
- CVE
- CVE-2020-8891
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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