SecurePoll Extension up to 1.35.1 on MediaWiki Vote information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in SecurePoll Extension up to 1.35.1 on MediaWiki. This affects an unknown function of the component Vote Handler. This manipulation causes information disclosure. The identification of this vulnerability is CVE-2020-35624. There is no exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in SecurePoll Extension up to 1.35.1 on MediaWiki (Survey Software). It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component Vote Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The weakness was shared 12/22/2020. The advisory is shared at phabricator.wikimedia.org. This vulnerability is known as CVE-2020-35624. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at gerrit.wikimedia.org.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.6
VulDB Base Score: 2.6
VulDB Temp Score: 2.6
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: gerrit.wikimedia.org
Timeline
12/22/2020 🔍12/22/2020 🔍
12/22/2020 🔍
Sources
Advisory: phabricator.wikimedia.orgStatus: Not defined
CVE: CVE-2020-35624 (🔍)
GCVE (CVE): GCVE-0-2020-35624
GCVE (VulDB): GCVE-100-166669
Entry
Created: 12/22/2020 08:17Changes: 12/22/2020 08:17 (39)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.