Crestron 3-Series Control Systems prior 1.8001.0187 BACnet Packet denial of service

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

Summaryinfo

A vulnerability has been found in Crestron 3-Series Control Systems and classified as problematic. Impacted is an unknown function of the component BACnet Packet Handler. This manipulation causes denial of service. The identification of this vulnerability is CVE-2023-38405. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Crestron 3-Series Control Systems. It has been declared as problematic. Affected by this vulnerability is an unknown part of the component BACnet Packet Handler. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:

On Crestron 3-Series Control Systems before 1.8001.0187, crafting and sending a specific BACnet packet can cause a crash.

The weakness was shared 07/18/2023. The advisory is shared at crestron.com. This vulnerability is known as CVE-2023-38405 since 07/17/2023. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.8001.0187 eliminates this vulnerability. The upgrade is hosted for download at crestron.com.

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

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Denial of service
CWE: CWE-404
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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: 3-Series Control Systems 1.8001.0187

Timelineinfo

07/17/2023 🔍
07/18/2023 +1 days 🔍
07/18/2023 +0 days 🔍
01/19/2026 +916 days 🔍

Sourcesinfo

Advisory: crestron.com
Status: Confirmed

CVE: CVE-2023-38405 (🔍)
GCVE (CVE): GCVE-0-2023-38405
GCVE (VulDB): GCVE-100-234349
EUVD: 🔍

Entryinfo

Created: 07/18/2023 10:02
Updated: 01/19/2026 07:21
Changes: 07/18/2023 10:02 (40), 08/09/2023 08:25 (11), 01/19/2026 07:21 (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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!