CVE-2023-25770
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 · uneditedController DoS may occur due to buffer overflow when an error is generated in response to a specially crafted message. See Honeywell Security Notification for recommendations on upgrading and versioning.
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 · moderate confidenceA buffer overflow vulnerability in Honeywell security controllers allows specially crafted messages to trigger a buffer overflow when the controller generates an error response, leading to denial of service of the controller.
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>= 501.1, <= 501.6hf8>= 510.1, <= 510.2hf12>= 511.1, <= 511.5tcu3>= 520.1, <= 520.1tcu4>= 520.2, <= 520.2tcu2CVSS 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 Honeywell C300 controller on the networkCheck your asset inventory or use network scanning tools to locate Honeywell C300 security controllers. Common methods include checking SNMP outputs, browsing Modbus/ proprietary protocol devices, or reviewing PLC/SCADA asset lists.Affected if A Honeywell C300 controller is found on the network and its firmware version falls within the affected ranges listed below.
-
Determine the firmware version of the C300 controllerAccess the controller through its management interface (Honeywell proprietary protocol, web interface if available, or through the engineering workstation). Navigate to the firmware or system information section to retrieve the exact firmware version string.Affected if The firmware version matches any of these ranges: 501.1 to 501.6hf8, 510.1 to 510.2hf12, 511.1 to 511.5tcu3, 520.1 to 520.1tcu4, or 520.2 to 520.2tcu2.
-
Verify if remote network communication is enabledCheck the controller network configuration settings to determine if inbound network communication from external sources is permitted. This typically involves reviewing the controller's communication module settings, firewall rules, or access control lists.Affected if The controller accepts network messages from untrusted sources, as the vulnerability is triggered by specially crafted messages sent to the controller.
-
Check if error response generation is activeReview the controller configuration to confirm that error response generation is enabled. In typical C300 configurations, this is handled by the controller's communication handler when processing invalid or malformed requests.Affected if The controller is configured to generate error responses to invalid messages, as this is the condition that triggers the buffer overflow during response construction.
A user is affected if they have a Honeywell C300 controller with firmware version within the listed ranges and the controller is accessible on the network to receive specially crafted messages.
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.
From vendor dataConsult the Honeywell Security Notification for specific affected models and apply available firmware updates to address the buffer overflow vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25770 — 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-25770 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