BACnet Protocol Stack up to 0.8.6 bacserv Daemon bacdcode.c out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in BACnet Protocol Stack up to 0.8.6. Affected by this vulnerability is an unknown functionality of the file bacdcode.c of the component bacserv Daemon. Such manipulation leads to out-of-bounds. This vulnerability is referenced as CVE-2019-12480. It is possible to launch the attack remotely. Furthermore, an exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in BACnet Protocol Stack up to 0.8.6. Affected by this issue is an unknown part of the file bacdcode.c of the component bacserv Daemon. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is availability. CVE summarizes:
BACnet Protocol Stack through 0.8.6 could allow an unauthenticated, remote attacker to cause a denial of service (bacserv daemon crash) because there is an invalid read in bacdcode.c during parsing of alarm tag numbers.
The weakness was published 05/30/2019. This vulnerability is handled as CVE-2019-12480 since 05/30/2019. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known.
The exploit is available at packetstormsecurity.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (47148). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/30/2019 🔍05/30/2019 🔍
05/31/2019 🔍
12/21/2024 🔍
Sources
Advisory: 153716Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-12480 (🔍)
GCVE (CVE): GCVE-0-2019-12480
GCVE (VulDB): GCVE-100-135740
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/31/2019 06:51Updated: 12/21/2024 14:30
Changes: 05/31/2019 06:51 (52), 06/17/2020 12:05 (1), 09/25/2023 11:17 (4), 06/16/2024 17:09 (22), 12/21/2024 14:30 (6)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.