Unauthenticated login bypass via loose hash comparison
Published Jan 27, 2021 · Updated Aug 4, 2024
Authentication bypass in Nibbleblog 3.7.1c allows remote attackers to authenticate through the admin login with a crafted password. In admin/kernel/api/login.class.php, verify_login hashes the supplied password with SHA-1 and loosely compares the result to the stored hash, so numeric-looking 0e hashes coerce to zero. Exploitation requires the stored hash and attacker-generated hash to use PHP's numeric 0e form; success creates an authenticated administrative session.
Summary
What happened
Authentication bypass in Nibbleblog 3.7.1c allows remote attackers to authenticate through the admin login with a crafted password. In admin/kernel/api/login.class.php, verify_login hashes the supplied password with SHA-1 and loosely compares the result to the stored hash, so numeric-looking 0e hashes coerce to zero. Exploitation requires the stored hash and attacker-generated hash to use PHP's numeric 0e form; success creates an authenticated administrative session.
The record
- CVE
- CVE-2020-23356
- Published
- Jan 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 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.
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