Sphinx up to 3.1.1 MySQL Client pathname traversal

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.
5.5$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Sphinx up to 3.1.1. This issue affects some unknown processing of the component MySQL Client. This manipulation causes pathname traversal. This vulnerability appears as CVE-2020-29050. There is no available exploit.

Detailsinfo

A vulnerability was found in Sphinx up to 3.1.1. It has been declared as critical. Affected by this vulnerability is some unknown processing of the component MySQL Client. The manipulation with an unknown input leads to a pathname traversal vulnerability. The CWE definition for the vulnerability is CWE-21. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was presented 01/10/2022. The advisory is shared at blog.wirhabenstil.de. This vulnerability is known as CVE-2020-29050 since 11/24/2020. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Pathname traversal
CWE: CWE-21 / CWE-22
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/24/2020 🔍
01/10/2022 +412 days 🔍
01/10/2022 +0 days 🔍
01/12/2022 +2 days 🔍

Sourcesinfo

Advisory: blog.wirhabenstil.de
Status: Not defined

CVE: CVE-2020-29050 (🔍)
GCVE (CVE): GCVE-0-2020-29050
GCVE (VulDB): GCVE-100-189853

Entryinfo

Created: 01/10/2022 17:17
Updated: 01/12/2022 08:55
Changes: 01/10/2022 17:17 (36), 01/12/2022 08:55 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!