MediaWiki up to 1.31.10/1.32.x/1.34.3 Actor ID exceptional condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.1$0-$5k0.00

Summaryinfo

A vulnerability was found in MediaWiki up to 1.31.10/1.32.x/1.34.3. It has been declared as problematic. Affected by this issue is some unknown functionality of the component Actor ID Handler. The manipulation results in an unknown weakness. This vulnerability is reported as CVE-2020-25869. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in MediaWiki up to 1.31.10/1.32.x/1.34.3 (Content Management System). It has been classified as problematic. Affected is some unknown processing of the component Actor ID Handler. CWE is classifying the issue as CWE-755. The product does not handle or incorrectly handles an exceptional condition. The impact remains unknown. CVE summarizes:

An information leak was discovered in MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4. Handling of actor ID does not necessarily use the correct database or correct wiki.

The weakness was disclosed 09/27/2020 (Website). The advisory is available at lists.wikimedia.org. This vulnerability is traded as CVE-2020-25869 since 09/24/2020. The technical details are unknown and an exploit is not available.

Upgrading to version 1.31.11 or 1.34.4 eliminates this vulnerability.

The entries VDB-162036, VDB-162037, VDB-162038 and VDB-162039 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB 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: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Exceptional condition
CWE: CWE-755
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: MediaWiki 1.31.11/1.34.4

Timelineinfo

09/24/2020 🔍
09/27/2020 +3 days 🔍
09/28/2020 +1 days 🔍
11/14/2020 +47 days 🔍

Sourcesinfo

Product: mediawiki.org

Advisory: lists.wikimedia.org
Status: Not defined
Confirmation: 🔍

CVE: CVE-2020-25869 (🔍)
GCVE (CVE): GCVE-0-2020-25869
GCVE (VulDB): GCVE-100-162042
See also: 🔍

Entryinfo

Created: 09/28/2020 07:22
Updated: 11/14/2020 18:20
Changes: 09/28/2020 07:22 (37), 09/28/2020 07:27 (3), 11/13/2020 07:58 (4), 11/14/2020 18:16 (1), 11/14/2020 18:20 (9)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!