Wikimedia MediaWiki up to 1.27.5/1.30.1/1.31.1/1.32.1 API information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Wikimedia MediaWiki up to 1.27.5/1.30.1/1.31.1/1.32.1 and classified as problematic. This vulnerability affects unknown code of the component API. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2019-12474. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Wikimedia MediaWiki up to 1.27.5/1.30.1/1.31.1/1.32.1 (Content Management System). It has been classified as problematic. This affects an unknown part of the component API. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
Wikimedia MediaWiki 1.23.0 through 1.32.1 has an information leak. Privileged API responses that include whether a recent change has been patrolled may be cached publicly. Fixed in 1.32.2, 1.31.2, 1.30.2 and 1.27.6.
The weakness was shared 07/10/2019 as not defined mailinglist post (Bugtraq). It is possible to read the advisory at seclists.org. This vulnerability is uniquely identified as CVE-2019-12474 since 05/30/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 176919 (Debian Security Update for mediawiki (DSA 4460-1)).
Upgrading to version 1.27.6, 1.30.2, 1.31.2 or 1.32.2 eliminates this vulnerability.
The entries VDB-137671, VDB-137672, VDB-137673 and VDB-137674 are related to this item. Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: MediaWiki 1.27.6/1.30.2/1.31.2/1.32.2
Timeline
05/30/2019 🔍07/10/2019 🔍
07/11/2019 🔍
07/07/2024 🔍
Sources
Advisory: seclists.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-12474 (🔍)
GCVE (CVE): GCVE-0-2019-12474
GCVE (VulDB): GCVE-100-137679
See also: 🔍
Entry
Created: 07/11/2019 11:15Updated: 07/07/2024 23:33
Changes: 07/11/2019 11:15 (42), 07/03/2020 17:02 (18), 07/07/2024 23:33 (18)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.