Remote service crash via unchecked APDU indexing
Published Dec 5, 2025 · Updated Dec 8, 2025
Out-of-bounds read in BACnet Stack before 1.5.0.rc2 allows remote attackers to crash strict builds via a malformed MS/TP frame. The npdu_is_expected_reply function indexes request and reply APDU bytes after a two-byte NPDU passes decoding, without checking that the indexed offsets exist. Reachability requires MS/TP traffic and a queued confirmed-service reply; strict builds abort, while unprotected builds can misroute replies.
Summary
What happened
Out-of-bounds read in BACnet Stack before 1.5.0.rc2 allows remote attackers to crash strict builds via a malformed MS/TP frame. The npdu_is_expected_reply function indexes request and reply APDU bytes after a two-byte NPDU passes decoding, without checking that the indexed offsets exist. Reachability requires MS/TP traffic and a queued confirmed-service reply; strict builds abort, while unprotected builds can misroute replies.
The record
- CVE
- CVE-2025-66624
- Published
- Dec 5, 2025
- Updated
- Dec 8, 2025
- Vendor
- BACnet Stack
- Product
- BACnet Stack
- Classifications
- CWE-125, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 5, 2025CVE publishedPublication date reported by the CVE source.
- Dec 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.5.0.rc2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Upstream MS/TP malformed-frame proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo