Username disclosure via default zero-token validation
Published Jun 21, 2021 · Updated Aug 4, 2024
Missing authentication in White Shark System 1.3.2 allows remote attackers to obtain all site usernames through if_get_addbook.php. The endpoint decodes attacker-supplied JSON, accepts the default token value 0, and passes the resulting user identifier to get_user_select, which returns the site's user list. No session or user interaction is required; exposure is limited to usernames, which can support account targeting.
Summary
What happened
Missing authentication in White Shark System 1.3.2 allows remote attackers to obtain all site usernames through if_get_addbook.php. The endpoint decodes attacker-supplied JSON, accepts the default token value 0, and passes the resulting user identifier to get_user_select, which returns the site's user list. No session or user interaction is required; exposure is limited to usernames, which can support account targeting.
The record
- CVE
- CVE-2020-20472
- Published
- Jun 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-306
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 21, 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
- Token-zero unauthenticated user-list requestproof of concept · demonstrated
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