Read the docs

BACnet Stack lets clients resize read-only files and read memory

Priority LOW 30CWE-284Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-284.

Summary

BACnet Stack before 1.5.1 does not check the Read_Only flag when a remote client changes the size of a stream-access FILE object (CWE-284). With the RAMFS backend, enlarging the file leaves the new tail bytes uninitialized, so a remote client can read them back with AtomicReadFile and receive stale heap contents or other process memory (CWE-908). A remote client can also shrink such a file and truncate content meant to be read-only.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to version 1.5.1, the BACnet FILE object implementation allows remote WriteProperty(PROP_FILE_SIZE) requests to change the size of a stream-access FILE object without checking whether that FILE is marked Read_Only. When the FILE backend is RAMFS, enlarging the file only performs realloc() and updates the stored size; the newly exposed tail region is not initialized before later reads. As a result, a remote client can enlarge a read-only RAMFS-backed stream-access FILE and then immediately retrieve the newly exposed region with AtomicReadFile(stream-access). Depending on the allocator and build configuration, the returned data may contain sanitizer fill bytes, stale heap contents, or other unintended process memory. Shrinking the file through the same path can also remotely truncate content that was intended to be read-only. This issue has been patched in versions 1.5.1 and 1.6.0.

Why it matters now

EPSS 0.00249 16th percentileScored 2026-11-16
Fix Fixed bacnet-stack (bacnet-stack): 1.5.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
bacnet-stackbacnet-stackbefore 1.5.11.5.1Patch availableCNA
  • bacnet-stack Vendorbacnet-stack Affected before 1.5.1 Fixed in 1.5.1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:bacnetstack:bacnet_stack:*:*:*:*:*:*:*:*——bacnet-stack
  • cpe:2.3:a:bacnetstack:bacnet_stack:*:*:*:*:*:*:*:* Versions — — ·bacnet-stack

Remediation

Upgrade bacnet-stack to version 1.5.1 or 1.6.0, which fix this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA bacnet-stack (bacnet-stack) Fixed in 1.5.1

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-62977

References

  • TI-2026-91748 Unbounded resize in BACnet Stack Structured View allows denial of service CVSS 4.0HIGH 8.7
  • TI-2026-30089 BACnet Stack: Out-of-Bounds Read in ReadPropertyMultiple Property Decoder via Deprecated Tag Parser CVSS 4.0HIGH 8.7
  • TI-2026-30088 BACnet Stack: Off-by-One Out-of-Bounds Read in ReadPropertyMultiple Object ID Decoder CVSS 4.0HIGH 8.7
  • TI-2026-30063 BACnet Stack: Out-of-Bounds Read in WritePropertyMultiple Decoder via Deprecated Tag Parser CVSS 4.0HIGH 8.7
  • TI-2026-91002 Stack-buffer-overflow in BACnet Stack Loop object description handling CVSS 3.1HIGH 8.2
  • TI-2026-91000 Stack-based buffer overflow in BACnet Stack Notification Class CVSS 3.1HIGH 8.2
See all 41 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences