Security readout for executives and security teams
Plain-English summary
This flaw can let a malformed BACnet packet crash Crestron 3-Series Control Systems running firmware before 1.8001.0187. The known impact is availability disruption, not confirmed data theft or device takeover. Evidence is limited to the CVE record and Crestron release notes.
Executive priority
Prioritize remediation where Crestron controllers support important building operations. The known business risk is service disruption from device crashes, with no source evidence of active exploitation.
Technical view
CVE-2023-38405 affects Crestron 3-Series Control Systems before 1.8001.0187. The issue is associated with CWE-770 and can be triggered by a specific BACnet packet, causing a crash. No CVSS score, detailed root cause, or public exploit evidence is provided in the source bundle.
Likely exposure
Organizations using Crestron 3-Series controllers with firmware older than 1.8001.0187 are the relevant exposure group, especially where controllers process BACnet traffic.
Exploitation context
The provided sources do not show CISA KEV listing, active exploitation, exploit availability, or attack complexity details. Treat this as a denial-of-service risk until vendor data says otherwise.
Researcher notes
Source evidence is sparse. The CVE names BACnet packet-triggered crash behavior and CWE-770 but does not provide packet details, CVSS scoring, affected model list, or exploit telemetry. Avoid assuming broader Crestron impact.
Mitigation direction
- Inventory Crestron 3-Series controllers and record firmware versions.
- Upgrade applicable devices to firmware 1.8001.0187 or later.
- Prioritize controllers reachable by BACnet or building automation networks.
- If upgrade timing is constrained, check Crestron guidance for compensating controls.
Validation and detection
- Confirm whether any Crestron 3-Series controllers run firmware before 1.8001.0187.
- Verify which controllers can receive BACnet traffic.
- Review operational history for unexplained controller crashes or reboots.
- Document remediation status and exceptions for vulnerability management tracking.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-38405 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.crestron.com/release_notes/cp3n_1.8001.0187_release_notes.pdfCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.