DYMO LabelWriter Print Server up to 2.366 hard-coded password

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

Summaryinfo

A vulnerability labeled as very critical has been found in DYMO LabelWriter Print Server up to 2.366. The impacted element is an unknown function. The manipulation results in hard-coded password. This vulnerability is reported as CVE-2023-49963. No exploit exists.

Detailsinfo

A vulnerability, which was classified as very critical, was found in DYMO LabelWriter Print Server up to 2.366. Affected is an unknown part. The manipulation with an unknown input leads to a hard-coded password vulnerability. CWE is classifying the issue as CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

DYMO LabelWriter Print Server through 2.366 contains a backdoor hard-coded password that could allow an attacker to take control.

This vulnerability is traded as CVE-2023-49963 since 12/04/2023. The exploitability is told to be easy. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/23/2024). This vulnerability is assigned to T1078.001 by the MITRE ATT&CK project.

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 best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.8

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

CNA Base Score: 8.8
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Hard-coded password
CWE: CWE-259 / CWE-255
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

12/04/2023 🔍
04/19/2024 +136 days 🔍
04/19/2024 +0 days 🔍
08/23/2024 +125 days 🔍

Sourcesinfo

Status: Not defined

CVE: CVE-2023-49963 (🔍)
GCVE (CVE): GCVE-0-2023-49963
GCVE (VulDB): GCVE-100-261642

Entryinfo

Created: 04/19/2024 19:48
Updated: 08/23/2024 00:50
Changes: 04/19/2024 19:48 (49), 08/23/2024 00:50 (11)
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.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!