CVE-2019-1659 Vulnerability Analysis & Exploit Details

CVE-2019-1659
Vulnerability Scoring

7.4
/10
Very High Risk

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

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and 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-1659 Details

Status: Modified

Last updated: 🕑 17 Jun 2026, 02:28 UTC
Originally published on: 🕒 21 Feb 2019, 15:29 UTC

Time between publication and last update: 2672 days

CVSS Release: version 3

CVSS3 Source

psirt@cisco.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2019-1659 Vulnerability Summary

CVE-2019-1659: A vulnerability in the Identity Services Engine (ISE) integration feature of Cisco Prime Infrastructure (PI) could allow an unauthenticated, remote attacker to perform a man-in-the-middle attack against the Secure Sockets Layer (SSL) tunnel established between ISE and PI. The vulnerability is due to improper validation of the server SSL certificate when establishing the SSL tunnel with ISE. An attacker could exploit this vulnerability by using a crafted SSL certificate and could then intercept communications between the ISE and PI. A successful exploit could allow the attacker to view and alter potentially sensitive information that the ISE maintains about clients that are connected to the network. This vulnerability affects Cisco Prime Infrastructure Software Releases 2.2 through 3.4.0 when the PI server is integrated with ISE, which is disabled by default.

Assessing the Risk of CVE-2019-1659

Access Complexity Graph

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

CVE-2019-1659 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

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

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

CVE-2019-1659 References

External References

CWE Common Weakness Enumeration

CWE-295

CAPEC Common Attack Pattern Enumeration and Classification

  • Creating a Rogue Certification Authority Certificate CAPEC-459 An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority.
  • Signature Spoofing by Improper Validation CAPEC-475 An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.

Vulnerable Configurations

  • cpe:2.3:a:cisco:prime_infrastructure:2.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.1:-:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.1:-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.1:update01:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.1:update01:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2\(2\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2\(2\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.2:-:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.2:-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.2:update03:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.2:update03:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.2:update04:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.2:update04:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2\(3\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2\(3\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.3:-:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.3:-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update02:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update02:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update03:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update03:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update04:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update04:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update05:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update05:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update06:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update06:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:2.2.10:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:2.2.10:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1\(0.0\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1\(0.0\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1\(0.128\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1\(0.128\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1\(4.0\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1\(4.0\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1\(5.0\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1\(5.0\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack10:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack10:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack11:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack11:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack12:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack12:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack13:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack13:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack14:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack14:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack15:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack15:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack16:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack16:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack4:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack5:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack5:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack6:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack6:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack7:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack7:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack8:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack8:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack9:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack9:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2.0-fips:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2.0-fips:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2\(0.0\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2\(0.0\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2\(1.0\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2\(1.0\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2\(2.0\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2\(2.0\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2:fips:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2:fips:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack1:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack2:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack3:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack3:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack4:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.3\(0.0\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.3\(0.0\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.3.0:update01:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.3.0:update01:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack1:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack2:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack3:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack3:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack4:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:prime_infrastructure:3.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:prime_infrastructure:3.4.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-1659: 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-2026-8023 – Zephyr's HTTP server (subsys/net/lib/http) provides a static-filesystem resource type (HTTP_RESOURCE_TYPE_STATIC_FS, available when CONFIG_FILE_SYS...
  • CVE-2026-7656 – The IPv6 Neighbor Discovery handlers in subsys/net/ip/ipv6_nbr.c (handle_ra_input, handle_ns_input, handle_na_input) used an incorrect boolean expr...
  • CVE-2026-51219 – A heap buffer overflow in the HighPriorityASDUQueue_hasUnconfirmedIMessages function of lib60870 v2.3.3 to v2.3.6 allows attackers to cause a Denia...
  • CVE-2026-51218 – A heap buffer overflow in the TS7Worker::PerformFunctionWrite() function (/core/s7_server.cpp) of snap7 v1.4.3 allows attackers to cause a Denial o...
  • CVE-2026-10648 – mcumgr_serial_process_frag() in subsys/mgmt/mcumgr/transport/src/serial_util.c calls net_buf_reset() on the result of smp_packet_alloc() before che...