CVE-2019-12674 Vulnerability Analysis & Exploit Details

CVE-2019-12674
Vulnerability Scoring

8.2
/10
Severe Risk

Cybersecurity professionals consider CVE-2019-12674 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2019-12674 Details

Status: Modified

Last updated: 🕓 21 Nov 2024, 04:23 UTC
Originally published on: 🕖 02 Oct 2019, 19:15 UTC

Time between publication and last update: 1876 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2019-12674 Vulnerability Summary

CVE-2019-12674: Multiple vulnerabilities in the multi-instance feature of Cisco Firepower Threat Defense (FTD) Software could allow an authenticated, local attacker to escape the container for their FTD instance and execute commands with root privileges in the host namespace. These vulnerabilities are due to insufficient protections on the underlying filesystem. An attacker could exploit these vulnerabilities by modifying critical files on the underlying filesystem. A successful exploit could allow the attacker to execute commands with root privileges within the host namespace. This could allow the attacker to impact other running FTD instances.

Assessing the Risk of CVE-2019-12674

Access Complexity Graph

The exploitability of CVE-2019-12674 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-12674

The exploitability of CVE-2019-12674 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

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-12674, 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-12674, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2019-12674 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2019-12674 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2019-12674 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: 0.042% (probability of exploit)

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

CVE-2019-12674 References

External References

CWE Common Weakness Enumeration

CWE-116

CAPEC Common Attack Pattern Enumeration and Classification

  • Cross Zone Scripting CAPEC-104 An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security.
  • User-Controlled Filename CAPEC-73 An attack of this type involves an adversary inserting malicious characters (such as a XSS redirection) into a filename, directly or indirectly that is then used by the target software to generate HTML text or other potentially executable content. Many websites rely on user-generated content and dynamically build resources like files, filenames, and URL links directly from user supplied data. In this attack pattern, the attacker uploads code that can execute in the client browser and/or redirect the client browser to a site that the attacker owns. All XSS attack payload variants can be used to pass and exploit these vulnerabilities.
  • Web Server Logs Tampering CAPEC-81 Web Logs Tampering attacks involve an attacker injecting, deleting or otherwise tampering with the contents of web logs typically for the purposes of masking other malicious behavior. Additionally, writing malicious data to log files may target jobs, filters, reports, and other agents that process the logs in an asynchronous attack pattern. This pattern of attack is similar to "Log Injection-Tampering-Forging" except that in this case, the attack is targeting the logs of the web server and not the application.
  • AJAX Footprinting CAPEC-85 This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.

Vulnerable Configurations

  • cpe:2.3:a:cisco:firepower_threat_defense:-:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:-:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:5.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:5.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:5.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:5.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.0.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.0.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.0.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.0.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.0.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.0.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.0.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.0.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.0.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.0.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.1.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.6:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.7:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.7:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.8:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.8:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.9:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.9:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.10:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.10:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.11:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.11:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.12:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.12:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.13:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.13:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.14:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.14:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.15:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.15:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.16:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.16:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.17:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.17:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.18:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.2.3.18:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.3.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:firepower_threat_defense:6.4.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:firepower_threat_defense:6.4.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:cisco:firepower_9300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:cisco:firepower_9300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:cisco:firepower_9300:-:*:*:*:*:*:*:*
    cpe:2.3:h:cisco:firepower_9300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:cisco:firepower_4115_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:cisco:firepower_4115_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:cisco:firepower_4115:-:*:*:*:*:*:*:*
    cpe:2.3:h:cisco:firepower_4115:-:*:*:*:*:*:*:*
  • cpe:2.3:o:cisco:firepower_4125_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:cisco:firepower_4125_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:cisco:firepower_4125:-:*:*:*:*:*:*:*
    cpe:2.3:h:cisco:firepower_4125:-:*:*:*:*:*:*:*
  • cpe:2.3:o:cisco:firepower_4145_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:cisco:firepower_4145_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:cisco:firepower_4145:-:*:*:*:*:*:*:*
    cpe:2.3:h:cisco:firepower_4145:-:*:*:*:*:*:*:*
  • cpe:2.3:o:cisco:firepower_4110_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:cisco:firepower_4110_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:cisco:firepower_4110:-:*:*:*:*:*:*:*
    cpe:2.3:h:cisco:firepower_4110:-:*:*:*:*:*:*:*
  • cpe:2.3:o:cisco:firepower_4120_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:cisco:firepower_4120_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:cisco:firepower_4120:-:*:*:*:*:*:*:*
    cpe:2.3:h:cisco:firepower_4120:-:*:*:*:*:*:*:*
  • cpe:2.3:o:cisco:firepower_4140_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:cisco:firepower_4140_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:cisco:firepower_4140:-:*:*:*:*:*:*:*
    cpe:2.3:h:cisco:firepower_4140:-:*:*:*:*:*:*:*
  • cpe:2.3:o:cisco:firepower_4150_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:cisco:firepower_4150_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:cisco:firepower_4150:-:*:*:*:*:*:*:*
    cpe:2.3:h:cisco:firepower_4150:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-12674: 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-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...