CVE-2020-15005
Description
From CVE.org
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.
Statement
The mediawiki package was removed from Red Hat OpenShift Container Platform in version 4.3.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.1 | 3.1 | N/A |
| Attack Vector | Network | Network | N/A |
| Attack Complexity | High | High | N/A |
| Privileges Required | None | None | N/A |
| User Interaction | Required | Required | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | Low | Low | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | None | None | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
NVD: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Red Hat CVSS v3 Score Explanation
Proposed changes to current CVSSv3 scoring: AC:L -> AC:H PR:L -> PR:N UI:N -> UI:R C:H -> C:L
To exploit this vulnerability an attacker needs to use an image URL which was already opened earlier by an authenticated/authorized user. When the authorized user views an image from a directories that are configured with $wgImgAuthUrlPathMap, then it may be cached in public cache. The attacker must guess what was the used URL. Hence proposing a change to Attack Complexity (AC) from Low to High and as the User Interaction is required proposing to change it from None to Required. The attacker don't need any privileges, hence the Privileges required should be None instead of Low. This vulnerability impacts the confidentiality, but the attacker can get access only to resources which were previously viewed, hence proposing to change the Confidentiality metric from High to Low.
We consider this as a Low impact flaw.
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
