CVE-2023-51773 Memory corruption in n/a
A buffer over-read in the BACnet Stack library allows attackers to cause denial of service or disclose sensitive memory contents.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2023-51773?
CVE-2023-51773 is a critical memory corruption vulnerability in n/a, published on 25 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
BACnet Stack before 1.3.2 has a decode function APDU buffer over-read in bacapp_decode_application_data in bacapp.c.
Weakness: CWE-126
Which versions are affected by CVE-2023-51773?
It affects 1 product.
Products include Bacnetstack Bacnet Stack.
How do I fix CVE-2023-51773?
No fix has been published for CVE-2023-51773 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2023-51773 being exploited?
There is no known exploitation of CVE-2023-51773 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2026-41475 BACnet Stack: Out-of-Bounds Read in WritePropertyMultiple Decoder via Deprecated Tag Parser
- CVE-2026-41502 BACnet Stack: Off-by-One Out-of-Bounds Read in ReadPropertyMultiple Object ID Decoder
- CVE-2026-41503 BACnet Stack: Out-of-Bounds Read in ReadPropertyMultiple Property Decoder via Deprecated Tag Parser
- CVE-2026-26264 BACnet Stack WriteProperty decoding length underflow leads to OOB read and crash
- CVE-2026-21878 BACnet Stack Improperly Limits Pathnames to a Restricted Directory
Sources
Also known as GHSA-3j77-72gm-5rj8.