Hero Qubo HCD01_02_V1.38_20220125 Telnet Service missing authentication

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

Summaryinfo

A vulnerability classified as critical has been found in Hero Qubo HCD01_02_V1.38_20220125. This vulnerability affects unknown code of the component Telnet Service. Performing a manipulation results in missing authentication. This vulnerability is reported as CVE-2023-22906. No exploit exists. It is suggested to use restrictive firewalling.

Detailsinfo

A vulnerability was found in Hero Qubo HCD01_02_V1.38_20220125. It has been classified as critical. This affects some unknown processing of the component Telnet Service. The manipulation with an unknown input leads to a missing authentication vulnerability. CWE is classifying the issue as CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Hero Qubo HCD01_02_V1.38_20220125 devices allow TELNET access with root privileges by default, without a password.

The weakness was disclosed 07/04/2023. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-22906 since 01/10/2023. Neither technical details nor an exploit are publicly available.

It is possible to mitigate the weakness by firewalling .

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-27008). If you want to get the best quality for vulnerability data then you always have to consider 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.5

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

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Missing authentication
CWE: CWE-306 / CWE-287
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: Firewall
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/10/2023 🔍
07/04/2023 +174 days 🔍
07/04/2023 +0 days 🔍
10/04/2025 +823 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2023-22906 (🔍)
GCVE (CVE): GCVE-0-2023-22906
GCVE (VulDB): GCVE-100-232917
EUVD: 🔍

Entryinfo

Created: 07/04/2023 07:25
Updated: 10/04/2025 23:54
Changes: 07/04/2023 07:25 (39), 07/23/2023 06:16 (10), 10/04/2025 23:54 (16)
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 ▸

Want to know what is going to be exploited?

We predict KEV entries!