Dentsply Sirona Sidexis up to 4.3 unquoted search path

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.
7.0$0-$5k0.85

Summaryinfo

A vulnerability has been found in Dentsply Sirona Sidexis up to 4.3 and classified as critical. This affects an unknown part. The manipulation leads to unquoted search path. This vulnerability is documented as CVE-2022-44264. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Dentsply Sirona Sidexis up to 4.3 and classified as critical. This issue affects an unknown part. The manipulation with an unknown input leads to a unquoted search path vulnerability. Using CWE to declare the problem leads to CWE-428. The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Dentsply Sirona Sidexis <= 4.3 is vulnerable to Unquoted Service Path.

The weakness was released 01/27/2023. It is possible to read the advisory at twitter.com. The identification of this vulnerability is CVE-2022-44264 since 10/30/2022. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1574.009 according to MITRE ATT&CK.

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

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.0
VulDB Meta Temp Score: 7.0

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

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Unquoted search path
CWE: CWE-428 / CWE-426
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/30/2022 🔍
01/27/2023 +89 days 🔍
01/27/2023 +0 days 🔍
04/01/2025 +795 days 🔍

Sourcesinfo

Advisory: twitter.com
Status: Not defined

CVE: CVE-2022-44264 (🔍)
GCVE (CVE): GCVE-0-2022-44264
GCVE (VulDB): GCVE-100-219551

Entryinfo

Created: 01/27/2023 11:15
Updated: 04/01/2025 02:16
Changes: 01/27/2023 11:15 (36), 02/23/2023 08:47 (11), 04/01/2025 02:16 (16)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!