An issue was discovered in the AbuseFilter extension for MediaWiki before 1.39.9, 1.40.x and 1.41.x before 1.41.3, and 1.42.x before 1.42.2. An API caller can match a filter condition against AbuseFilter logs even if the caller is not authorized to view the log details for the filter.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Mediawiki | Mediawiki | * | 1.39.9 (excluding) |
| Mediawiki | Mediawiki | 1.40.0 (including) | 1.41.3 (excluding) |
| Mediawiki | Mediawiki | 1.42.0 (including) | 1.42.2 (excluding) |
| Mediawiki | Ubuntu | focal | * |
| Mediawiki | Ubuntu | oracular | * |
| Mediawiki | Ubuntu | upstream | * |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: