CVE-2019-12480 Vulnerability Analysis & Exploit Details

CVE-2019-12480
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2019-12480 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2019-12480 Details

Status: Modified

Last updated: 🕓 21 Nov 2024, 04:22 UTC
Originally published on: 🕙 30 May 2019, 22:29 UTC

Time between publication and last update: 2001 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE-2019-12480 Vulnerability Summary

CVE-2019-12480: 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.

Assessing the Risk of CVE-2019-12480

Access Complexity Graph

The exploitability of CVE-2019-12480 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2019-12480

With low attack complexity and no required privileges, CVE-2019-12480 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2019-12480, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2019-12480, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2019-12480 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2019-12480 poses no threat to data integrity.
  • Availability: High
    CVE-2019-12480 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 6.183% (probability of exploit)

EPSS Percentile: 93.64% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 6.359999999999999% of others.

CVE-2019-12480 References

External References

CWE Common Weakness Enumeration

CWE-125

CAPEC Common Attack Pattern Enumeration and Classification

  • Overread Buffers CAPEC-540 An adversary attacks a target by providing input that causes an application to read beyond the boundary of a defined buffer. This typically occurs when a value influencing where to start or stop reading is set to reflect positions outside of the valid memory location of the buffer. This type of attack may result in exposure of sensitive information, a system crash, or arbitrary code execution.

Vulnerable Configurations

  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.6:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.5:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.6:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.7:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.7:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.8:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.8:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.9:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.5.9:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.4:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.5:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.7.5:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.5:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.5:*:*:*:*:*:*:*
  • cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.6:*:*:*:*:*:*:*
    cpe:2.3:a:bacnet_protocol_stack_project:bacnet_protocol_stack:0.8.6:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-12480: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...