MediaWiki up to 1.19.17/1.22.8/1.23.1 OutputPage/ParserOutput privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in MediaWiki up to 1.19.17/1.22.8/1.23.1. Affected by this vulnerability is the function OutputPage/ParserOutput. The manipulation leads to privileges management.
No exploit is available.
You should upgrade the affected component.
Details
A vulnerability was found in MediaWiki up to 1.19.17/1.22.8/1.23.1 (Content Management System). It has been rated as problematic. This issue affects the function OutputPage/ParserOutput. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is integrity.
The weakness was published 07/30/2014 as Bug 65778 / MediaWiki Security and Maintenance Releases: 1.19.18, 1.22.9 and 1.23.2 as confirmed posting (Mailing List). The advisory is shared at lists.wikimedia.org. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 1.23.2, 1.22.9 or 1.19.18 eliminates this vulnerability. The upgrade is hosted for download at releases.wikimedia.org. Applying a patch is able to eliminate this problem. The bugfix is ready for download at releases.wikimedia.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityTracker (ID 1030660†). Similar entries are available at VDB-67264 and VDB-67263. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 1.19.0
- 1.19.1
- 1.19.2
- 1.19.3
- 1.19.4
- 1.19.5
- 1.19.6
- 1.19.7
- 1.19.8
- 1.19.9
- 1.19.10
- 1.19.11
- 1.19.12
- 1.19.13
- 1.19.14
- 1.19.15
- 1.19.16
- 1.19.17
- 1.22.0
- 1.22.1
- 1.22.2
- 1.22.3
- 1.22.4
- 1.22.5
- 1.22.6
- 1.22.7
- 1.22.8
- 1.23.0
- 1.23.1
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: MediaWiki 1.23.2/1.22.9/1.19.18
Patch: releases.wikimedia.org
Timeline
07/30/2014 🔍07/30/2014 🔍
08/01/2014 🔍
08/04/2014 🔍
04/19/2019 🔍
Sources
Product: mediawiki.orgAdvisory: Bug 65778 / MediaWiki Security and Maintenance Releases: 1.19.18, 1.22.9 and 1.23.2
Status: Confirmed
GCVE (VulDB): GCVE-100-67265
SecurityTracker: 1030660
See also: 🔍
Entry
Created: 08/04/2014 10:09Updated: 04/19/2019 11:22
Changes: 08/04/2014 10:09 (45), 04/19/2019 11:22 (4)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.