LS ELECTRIC XBC-DN32U 01.80 access of memory location after end of buffer

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

Summaryinfo

A vulnerability has been found in LS ELECTRIC XBC-DN32U 01.80 and classified as critical. This affects an unknown function. This manipulation causes access of memory location after end of buffer. The identification of this vulnerability is CVE-2023-0103. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in LS ELECTRIC XBC-DN32U 01.80. It has been declared as critical. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a access of memory location after end of buffer vulnerability. The CWE definition for the vulnerability is CWE-788. The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer. As an impact it is known to affect availability. The summary by CVE is:

If an attacker were to access memory locations of LS ELECTRIC XBC-DN32U with operating system version 01.80 that are outside of the communication buffer, the device stops operating. This could allow an attacker to cause a denial-of-service condition.

The weakness was shared 02/15/2023 as icsa-23-040-02. It is possible to read the advisory at cisa.gov. This vulnerability is known as CVE-2023-0103 since 01/06/2023. The technical details are unknown and an exploit is not publicly available.

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.5
VulDB Meta Temp Score: 7.3

VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 7.5
CNA Vector (ICS-CERT): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Access of memory location after end of buffer
CWE: CWE-788 / CWE-120 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
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

01/06/2023 🔍
02/15/2023 +40 days 🔍
02/15/2023 +0 days 🔍
02/15/2023 +0 days 🔍

Sourcesinfo

Advisory: icsa-23-040-02
Status: Not defined

CVE: CVE-2023-0103 (🔍)
GCVE (CVE): GCVE-0-2023-0103
GCVE (VulDB): GCVE-100-221119

Entryinfo

Created: 02/15/2023 22:01
Changes: 02/15/2023 22:01 (47)
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 ▸

Want to know what is going to be exploited?

We predict KEV entries!