VDB-223989 · CVE-2023-23149 · EUVD-2023-27249

DEK-1705 up to 34.23.1 command injection

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.5	$0-$5k	0.00

Summaryinfo

A vulnerability has been found in DEK-1705 up to 34.23.1 and classified as problematic. The impacted element is an unknown function. Performing a manipulation results in an unknown weakness. This vulnerability is cataloged as CVE-2023-23149. There is no exploit available.

Detailsinfo

A vulnerability was found in DEK-1705 up to 34.23.1. It has been classified as problematic. CWE is classifying the issue as CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

DEK-1705 <=Firmware:34.23.1 device was discovered to have a command execution vulnerability.

The weakness was shared 03/25/2023. The advisory is shared at gist.github.com. This vulnerability is uniquely identified as CVE-2023-23149 since 01/11/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1202 for this issue.

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

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-27249). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

DEK-1705

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.6

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

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Command injection
CWE: CWE-77 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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 Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/11/2023 🔍
03/25/2023 +73 days 🔍
03/25/2023 +0 days 🔍
10/06/2025 +926 days 🔍

Sourcesinfo

Advisory: gist.github.com
Status: Not defined

CVE: CVE-2023-23149 (🔍)
GCVE (CVE): GCVE-0-2023-23149
GCVE (VulDB): GCVE-100-223989
EUVD: 🔍

Entryinfo

Created: 03/25/2023 09:19
Updated: 10/06/2025 17:06
Changes: 03/25/2023 09:19 (34), 04/15/2023 09:09 (12), 10/06/2025 17:06 (16)
Complete: 🔍
Cache ID: 216::103

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