BACnet Stack up to 1.3.1 APDU bacapp.c bacapp_decode_application_data buffer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in BACnet Stack up to 1.3.1. It has been classified as critical. This affects the function bacapp_decode_application_data of the file bacapp.c of the component APDU Handler. Performing a manipulation results in buffer overflow.
This vulnerability is cataloged as CVE-2023-51773. There is no exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in BACnet Stack up to 1.3.1. It has been classified as critical. This affects the function bacapp_decode_application_data of the file bacapp.c of the component APDU Handler. The manipulation with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
BACnet Stack before 1.3.2 has a decode function APDU buffer over-read in bacapp_decode_application_data in bacapp.c.
The weakness was shared 12/25/2023. The advisory is shared at sourceforge.net. This vulnerability is uniquely identified as CVE-2023-51773. Technical details are known, but no exploit is available.
Upgrading to version 1.3.2 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Stack 1.3.2
Patch: github.com
Timeline
12/25/2023 🔍12/25/2023 🔍
12/25/2023 🔍
05/24/2025 🔍
Sources
Advisory: sourceforge.netStatus: Confirmed
CVE: CVE-2023-51773 (🔍)
GCVE (CVE): GCVE-0-2023-51773
GCVE (VulDB): GCVE-100-249009
Entry
Created: 12/25/2023 22:25Updated: 05/24/2025 00:44
Changes: 12/25/2023 22:25 (41), 01/19/2024 09:21 (2), 05/24/2025 00:44 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.