CVE-2023-38405
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOn Crestron 3-Series Control Systems before 1.8001.0187, crafting and sending a specific BACnet packet can cause a crash.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA Denial of Service vulnerability exists in Crestron 3-Series Control Systems where crafting and sending a specific BACnet packet triggers a crash in the BACnet service. The vulnerability is network-exploitable and requires no authentication, allowing remote attackers to cause the device to become unavailable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.8001.0187< 1.8001.0187< 1.8001.0187CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Crestron 3-Series modelAccess the device web interface or connect via SSH/serial console and locate the model number (Cp3n, Cp3, or Cp3 Gv) in the system information or device status pageAffected if The model is a Crestron Cp3n (6505417), Cp3 (6504877), or Cp3 Gv (6506034)
-
Check the installed firmware versionIn the device web interface, navigate to System Information or Diagnostics. Alternatively, via SSH or serial console, use the 'sysinfo' command or check the firmware version displayed at loginAffected if The firmware version is lower than 1.8001.0187
-
Verify BACnet service is enabledIn the device web interface, navigate to Device Settings or Communication Settings and confirm if BACnet is enabled. Alternatively, check via SSH using commands like 'bacnet show' or 'enumerate bma' if availableAffected if BACnet is enabled and configured on the device
-
Confirm network accessibility of BACnet portFrom a networked host, attempt to reach the BACnet port (default UDP 47808) on the device using 'nc -uz <device_ip> 47808' or nmap -sU -p 47808 <device_ip>Affected if The BACnet UDP port 47808 is open and reachable from an untrusted network
You are affected if you have a Crestron Cp3n, Cp3, or Cp3 Gv device with firmware below version 1.8001.0187 and BACnet is enabled and accessible on your network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.8001.0187
Update Crestron 3-Series Control Systems firmware to version 1.8001.0187 or later. If immediate patching is not possible, consider network segmentation to limit exposure of BACnet services to untrusted networks.
Crestron 3-Series Control Systems Firmware 1.8001.0187
- Download the firmware version 1.8001.0187 or later from the official Crestron support website
- Access the Crestron 3-Series Control System web interface or use Crestron Toolbox
- Navigate to the firmware upgrade section
- Upload and apply the firmware version 1.8001.0187
- Verify the firmware was applied successfully by checking the system information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38405 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-38405 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data