GHSA-xpv7-93cm-4mxv BIT-mediawiki-2020-15005 CVE-2020-15005
img_auth.php may leak private extension images into the public cache
- Severity
- Medium
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 1.30%
- Chance of exploitation in the next 30 days. Higher than 70.48% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
1.31.8- Upgrade mediawiki/core to this version or later
Description
In MediaWiki before 1.31.8, 1.32.x and 1.33.x before 1.33.4, and 1.34.x before 1.34.2, private wikis behind a caching server using the img_auth.php image authorization security feature may have had their files cached publicly, so any unauthorized user could view them. This occurs because Cache-Control and Vary headers were mishandled.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| mediawiki/core | < 1.31.8 |
1.31.8 |
| mediawiki/core | >= 1.32.0, < 1.33.4 |
1.33.4 |
| mediawiki/core | >= 1.34.0, < 1.34.2 |
1.34.2 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
mediawiki/core Packagist → 1.31.8
- composer
composer require mediawiki/core:^1.31.8
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
- gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/REL1_31/RELEASE-NOTES-1.31
- gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/REL1_33/RELEASE-NOTES-1.33
- gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/REL1_34/RELEASE-NOTES-1.34
- lists.debian.org/debian-lts-announce/2020/12/msg00034.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EEZIM…
- lists.wikimedia.org/pipermail/wikitech-l/2020-June/093535.html
- phabricator.wikimedia.org/T248947
- debian.org/security/2020/dsa-4767
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-w5fx-cx7f-6vr9 MediaWiki Denial of Service vulnerability | High | Also affects mediawiki/core |
| GHSA-5vj8-g3qg-4qh6 X-Forwarded-For header allows brute-forcing autoblocked IP addresses | Critical | Also affects mediawiki/core |
| GHSA-c8wv-qwwc-6j73 MediaWiki allows a denial of service | Medium | Also affects mediawiki/core |
| GHSA-rqvj-fc2x-99q6 OATHAuth extension in MediaWiki is not implementing rate limit | High | Also affects mediawiki/core |
| GHSA-c4rj-wrmq-52rj MediaWiki Special:UserRights exposes the existence of hidden users | Medium | Also affects mediawiki/core |
| GHSA-h8qx-mj6v-2934 MediaWiki Cross-site Scripting (XSS) vulnerability | Medium | Also affects mediawiki/core |
| GHSA-4vr7-m8p8-434h MediaWiki Cross-site Scripting (XSS) vulnerability | Medium | Also affects mediawiki/core |
| GHSA-2f58-vf6g-6p8x MediaWiki Cross-site Scripting (XSS) vulnerability | Medium | Also affects mediawiki/core |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor