CVE-2019-1692 Security Vulnerability & Exploit Details

CVE-2019-1692
Vulnerability Scoring

5.3

/10

Significant Risk

Security assessments indicate that CVE-2019-1692 presents a notable risk, potentially requiring prompt mitigation.

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-1692 Details

Status: Modified

Last updated: 🕟 21 Nov 2024, 04:37 UTC
Originally published on: 🕒 03 May 2019, 15:29 UTC

Time between publication and last update: 2028 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2019-1692 Vulnerability Summary

CVE-2019-1692: A vulnerability in the web-based management interface of Cisco Application Policy Infrastructure Controller (APIC) Software could allow an unauthenticated, remote attacker to access sensitive system usage information. The vulnerability is due to a lack of proper data protection mechanisms for certain components in the underlying Application Centric Infrastructure (ACI). An attacker could exploit this vulnerability by attempting to observe certain network traffic when accessing the APIC. A successful exploit could allow the attacker to access and collect certain tracking data and usage statistics on an affected device.

Assessing the Risk of CVE-2019-1692

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2019-1692 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-1692, 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-1692, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: Low
CVE-2019-1692 could lead to minor leaks of non-critical information without major privacy breaches.
Integrity: None
CVE-2019-1692 poses no threat to data integrity.
Availability: None
CVE-2019-1692 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.079% (probability of exploit)

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

CVE-2019-1692 References

External References

CWE Common Weakness Enumeration

CWE-311

CAPEC Common Attack Pattern Enumeration and Classification

Sniffing Attacks CAPEC-157 In this attack pattern, the adversary intercepts information transmitted between two third parties. The adversary must be able to observe, read, and/or hear the communication traffic, but not necessarily block the communication or change its content. Any transmission medium can theoretically be sniffed if the adversary can examine the contents between the sender and recipient. Sniffing Attacks are similar to Adversary-In-The-Middle attacks (CAPEC-94), but are entirely passive. AiTM attacks are predominantly active and often alter the content of the communications themselves.
Sniffing Network Traffic CAPEC-158 In this attack pattern, the adversary monitors network traffic between nodes of a public or multicast network in an attempt to capture sensitive information at the protocol level. Network sniffing applications can reveal TCP/IP, DNS, Ethernet, and other low-level network communication information. The adversary takes a passive role in this attack pattern and simply observes and analyzes the traffic. The adversary may precipitate or indirectly influence the content of the observed transaction, but is never the intended recipient of the target information.
Lifting Sensitive Data Embedded in Cache CAPEC-204 An adversary examines a target application's cache, or a browser cache, for sensitive information. Many applications that communicate with remote entities or which perform intensive calculations utilize caches to improve efficiency. However, if the application computes or receives sensitive information and the cache is not appropriately protected, an attacker can browse the cache and retrieve this information. This can result in the disclosure of sensitive information.
Accessing/Intercepting/Modifying HTTP Cookies CAPEC-31 This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.
Retrieve Embedded Sensitive Data CAPEC-37 An attacker examines a target system to find sensitive data that has been embedded within it. This information can reveal confidential contents, such as account numbers or individual keys/credentials that can be used as an intermediate step in a larger attack.
Harvesting Information via API Event Monitoring CAPEC-383 An adversary hosts an event within an application framework and then monitors the data exchanged during the course of the event for the purpose of harvesting any important data leaked during the transactions. One example could be harvesting lists of usernames or userIDs for the purpose of sending spam messages to those users. One example of this type of attack involves the adversary creating an event within the sub-application. Assume the adversary hosts a "virtual sale" of rare items. As other users enter the event, the attacker records via AiTM (CAPEC-94) proxy the user_ids and usernames of everyone who attends. The adversary would then be able to spam those users within the application using an automated script.
Application API Message Manipulation via Man-in-the-Middle CAPEC-384 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack can allow the attacker to gain unauthorized privileges within the application, or conduct attacks such as phishing, deceptive strategies to spread malware, or traditional web-application attacks. The techniques require use of specialized software that allow the attacker to perform adversary-in-the-middle (CAPEC-94) communications between the web browser and the remote system. Despite the use of AiTH software, the attack is actually directed at the server, as the client is one node in a series of content brokers that pass information along to the application framework. Additionally, it is not true "Adversary-in-the-Middle" attack at the network layer, but an application-layer attack the root cause of which is the master applications trust in the integrity of code supplied by the client.
Transaction or Event Tampering via Application API Manipulation CAPEC-385 An attacker hosts or joins an event or transaction within an application framework in order to change the content of messages or items that are being exchanged. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, substitute one item or another, spoof an existing item and conduct a false exchange, or otherwise change the amounts or identity of what is being exchanged. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the content of various application elements. Often, items exchanged in game can be monetized via sales for coin, virtual dollars, etc. The purpose of the attack is for the attack to scam the victim by trapping the data packets involved the exchange and altering the integrity of the transfer process.
Application API Navigation Remapping CAPEC-386 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of links/buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains links/buttons that point to an attacker controlled destination. Some applications make navigation remapping more difficult to detect because the actual HREF values of images, profile elements, and links/buttons are masked. One example would be to place an image in a user's photo gallery that when clicked upon redirected the user to an off-site location. Also, traditional web vulnerabilities (such as CSRF) can be constructed with remapped buttons or links. In some cases navigation remapping can be used for Phishing attacks or even means to artificially boost the page view, user site reputation, or click-fraud.
Navigation Remapping To Propagate Malicious Content CAPEC-387 An adversary manipulates either egress or ingress data from a client within an application framework in order to change the content of messages and thereby circumvent the expected application logic.
Application API Button Hijacking CAPEC-388 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains buttons that point to an attacker controlled destination.
Signature Spoofing by Mixing Signed and Unsigned Content CAPEC-477 An attacker exploits the underlying complexity of a data structure that allows for both signed and unsigned content, to cause unsigned data to be processed as though it were signed data.
Cellular Traffic Intercept CAPEC-609 Cellular traffic for voice and data from mobile devices and retransmission devices can be intercepted via numerous methods. Malicious actors can deploy their own cellular tower equipment and intercept cellular traffic surreptitiously. Additionally, government agencies of adversaries and malicious actors can intercept cellular traffic via the telecommunications backbone over which mobile traffic is transmitted.
Sniff Application Code CAPEC-65 An adversary passively sniffs network communications and captures application code bound for an authorized client. Once obtained, they can use it as-is, or through reverse-engineering glean sensitive information or exploit the trust relationship between the client and server. Such code may belong to a dynamic update to the client, a patch being applied to a client component or any such interaction where the client is authorized to communicate with the server.

Vulnerable Configurations

cpe:2.3:a:cisco:application_policy_infrastructure_controller:-:*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:-:*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(1e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(1e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(1h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(1h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(1k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(1k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(1n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(1n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(2j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(2j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(2m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(2m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(3o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(4h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(4h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(4o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(4o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(4q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.0\(4q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(0.920a\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(0.920a\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(0c\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(0c\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(1j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(1j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(1o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(1o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(1r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(1r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(1s\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(1s\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(2h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(2h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(2i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(2i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1.3:c:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1.3:c:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1.3:d:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1.3:d:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(3f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(3f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4g\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4g\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.1\(4m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(1m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(1m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(2\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(2\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2.2:*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2.2:*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(2i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(2i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(2j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(2j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(3\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(3\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(3h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(3h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(3m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2\(3m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(1\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(1\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(1i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(1i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(1j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(1j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.3\(2k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2_base:*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:1.2_base:*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(1r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2g\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2g\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0\(2o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(1i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(1i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(2e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(2e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(2g\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(2g\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(2k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(2k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(3g\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(3g\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(3h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(3h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(3j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(3j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(4a\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.1\(4a\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(1o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(1o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(2q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3j\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3s\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3s\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3t\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(3t\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(4f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(4f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(4p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(4p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(4q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(4q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(4r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.2\(4r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.3\(1p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0_base:*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:2.0_base:*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(1k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(1k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(2h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(2h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(2k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(2k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(2n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(2n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(3i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.0\(3i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(1i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(1i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2p\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2q\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2s\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2s\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2t\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2t\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2u\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2u\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2v\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.1\(2v\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(1l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(1l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(1m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(1m\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(2l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(2l\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(2o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(2o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3n\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3o\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3r\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3s\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(3s\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(4d\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(4d\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(4e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(4e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(5d\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(5d\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(5e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(5e\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(5f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(5f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(6i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(6i\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(7f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(7f\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(7k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(7k\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(9b\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:3.2\(9b\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.0\(1h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.0\(1h\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.0\(2c\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.0\(2c\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.0\(3d\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.0\(3d\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.1\(0.88a\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.1\(0.88a\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.1\(0.90a\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.1\(0.90a\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.1\(1\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:4.1\(1\):*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:8.3\(1\)s6:*:*:*:*:*:*:*
cpe:2.3:a:cisco:application_policy_infrastructure_controller:8.3\(1\)s6:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-1692: 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-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...
CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...

CVE-2019-1692 Vulnerability Scoring