Sensitive-data disclosure via unsuppressed AbuseLog revisions
Published Mar 20, 2020 · Updated Aug 5, 2024
Information disclosure in Wikimedia AbuseFilter REL1_32 and REL1_33 allows remote attackers to view suppressed usernames and edit summaries. SpecialAbuseLog.php exposes AbuseLog revision metadata without honoring the suppression applied to the user who performed the recorded edit. No authentication or user interaction is required; exposure is limited to suppressed usernames and summaries present in affected log revisions.
Summary
What happened
Information disclosure in Wikimedia AbuseFilter REL1_32 and REL1_33 allows remote attackers to view suppressed usernames and edit summaries. SpecialAbuseLog.php exposes AbuseLog revision metadata without honoring the suppression applied to the user who performed the recorded edit. No authentication or user interaction is required; exposure is limited to suppressed usernames and summaries present in affected log revisions.
The record
- CVE
- CVE-2019-16528
- Published
- Mar 20, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-532, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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