Skip to content
Fencer Intel
high 7.5

CVE-2019-12480 in the critical feed json

BACnet Protocol Stack through 0.8.6 has a segmentation fault leading to denial of service in BACnet APDU Layer because a malformed DCC in A…

published 7y ago modified 4mo ago also EUVD-2019-4076

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
33.9%
EPSS 33.9% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

BACnet Protocol Stack through 0.8.6 has a segmentation fault leading to denial of service in BACnet APDU Layer because a malformed DCC in AtomicWriteFile, AtomicReadFile and DeviceCommunicationControl services. An unauthenticated remote attacker could cause a denial of service (bacserv daemon crash) because there is an invalid read in bacdcode.c during parsing of alarm tag numbers.

Is CVE-2019-12480 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-47148)

Exploit prediction

33.89% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-47148 BACnet Stack 0.8.6 - Denial of Service dos, 2019-07-22
  • sourceforge.net https://sourceforge.net/p/bacnet/bugs/62/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.