# CVE-2019-12480: Denial of service in n/a

> An unauthenticated remote attacker can crash the BACnet service daemon via malformed packets, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cc8w-j726-c7gj

## What is CVE-2019-12480?

CVE-2019-12480 is a high-severity denial of service vulnerability in n/a, published on 30 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-12480?

It affects 1 product.


Products: Bacnet Protocol Stack Project Bacnet Protocol Stack.

## How do I fix CVE-2019-12480?

No fix has been published for CVE-2019-12480 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-12480 being exploited?

There is no known exploitation of CVE-2019-12480 in the wild and no public exploit code.

Public exploit code:

- BACnet Stack 0.8.6 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-10238](https://insights.sbomify.com/CVE-2018-10238/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12480 and fix it if it is affected.

What it is: CVE-2019-12480 is a high-severity denial of service vulnerability in n/a, published on 30 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12480 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-12480/ (Markdown: https://insights.sbomify.com/CVE-2019-12480/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-12480
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-12480
- OSV: https://osv.dev/vulnerability/CVE-2019-12480

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-12480/
Summaries are generated and may contain mistakes; the official description above is the record.