CVE-2019-19300 Vulnerability Analysis & Exploit Details

CVE-2019-19300
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2019-19300 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-19300 Details

Status: Modified

Last updated: 🕛 09 Jul 2024, 12:15 UTC
Originally published on: 🕗 14 Apr 2020, 20:15 UTC

Time between publication and last update: 1546 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:N/I:N/A:H

CVE-2019-19300 Vulnerability Summary

CVE-2019-19300: A vulnerability has been identified in Development/Evaluation Kits for PROFINET IO: EK-ERTEC 200, Development/Evaluation Kits for PROFINET IO: EK-ERTEC 200P, KTK ATE530S, SIDOOR ATD430W, SIDOOR ATE530S COATED, SIDOOR ATE531S, SIMATIC ET 200AL IM 157-1 PN (6ES7157-1AB00-0AB0), SIMATIC ET 200MP IM 155-5 PN HF (6ES7155-5AA00-0AC0), SIMATIC ET 200pro IM 154-8 PN/DP CPU (6ES7154-8AB01-0AB0), SIMATIC ET 200pro IM 154-8F PN/DP CPU (6ES7154-8FB01-0AB0), SIMATIC ET 200pro IM 154-8FX PN/DP CPU (6ES7154-8FX00-0AB0), SIMATIC ET 200S IM 151-8 PN/DP CPU (6ES7151-8AB01-0AB0), SIMATIC ET 200S IM 151-8F PN/DP CPU (6ES7151-8FB01-0AB0), SIMATIC ET 200SP IM 155-6 MF HF (6ES7155-6MU00-0CN0), SIMATIC ET 200SP IM 155-6 PN HA (incl. SIPLUS variants), SIMATIC ET 200SP IM 155-6 PN HF (6ES7155-6AU00-0CN0), SIMATIC ET 200SP IM 155-6 PN/2 HF (6ES7155-6AU01-0CN0), SIMATIC ET 200SP IM 155-6 PN/3 HF (6ES7155-6AU30-0CN0), SIMATIC ET 200SP Open Controller CPU 1515SP PC (incl. SIPLUS variants), SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants), SIMATIC ET200ecoPN, AI 8xRTD/TC, M12-L (6ES7144-6JF00-0BB0), SIMATIC ET200ecoPN, CM 4x IO-Link, M12-L (6ES7148-6JE00-0BB0), SIMATIC ET200ecoPN, CM 8x IO-Link, M12-L (6ES7148-6JG00-0BB0), SIMATIC ET200ecoPN, CM 8x IO-Link, M12-L (6ES7148-6JJ00-0BB0), SIMATIC ET200ecoPN, DI 16x24VDC, M12-L (6ES7141-6BH00-0BB0), SIMATIC ET200ecoPN, DI 8x24VDC, M12-L (6ES7141-6BG00-0BB0), SIMATIC ET200ecoPN, DIQ 16x24VDC/2A, M12-L (6ES7143-6BH00-0BB0), SIMATIC ET200ecoPN, DQ 8x24VDC/0,5A, M12-L (6ES7142-6BG00-0BB0), SIMATIC ET200ecoPN, DQ 8x24VDC/2A, M12-L (6ES7142-6BR00-0BB0), SIMATIC MICRO-DRIVE PDC, SIMATIC PN/MF Coupler (6ES7158-3MU10-0XA0), SIMATIC PN/PN Coupler (6ES7158-3AD10-0XA0), SIMATIC S7-1200 CPU family (incl. SIPLUS variants), SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants), SIMATIC S7-1500 Software Controller, SIMATIC S7-300 CPU 314C-2 PN/DP (6ES7314-6EH04-0AB0), SIMATIC S7-300 CPU 315-2 PN/DP (6ES7315-2EH14-0AB0), SIMATIC S7-300 CPU 315F-2 PN/DP (6ES7315-2FJ14-0AB0), SIMATIC S7-300 CPU 315T-3 PN/DP (6ES7315-7TJ10-0AB0), SIMATIC S7-300 CPU 317-2 PN/DP (6ES7317-2EK14-0AB0), SIMATIC S7-300 CPU 317F-2 PN/DP (6ES7317-2FK14-0AB0), SIMATIC S7-300 CPU 317T-3 PN/DP (6ES7317-7TK10-0AB0), SIMATIC S7-300 CPU 317TF-3 PN/DP (6ES7317-7UL10-0AB0), SIMATIC S7-300 CPU 319-3 PN/DP (6ES7318-3EL01-0AB0), SIMATIC S7-300 CPU 319F-3 PN/DP (6ES7318-3FL01-0AB0), SIMATIC S7-400 H V6 and below CPU family (incl. SIPLUS variants), SIMATIC S7-400 PN/DP V7 CPU family (incl. SIPLUS variants), SIMATIC S7-410 V10 CPU family (incl. SIPLUS variants), SIMATIC S7-410 V8 CPU family (incl. SIPLUS variants), SIMATIC TDC CP51M1, SIMATIC TDC CPU555, SIMATIC WinAC RTX 2010 (6ES7671-0RC08-0YA0), SIMATIC WinAC RTX F 2010 (6ES7671-1RC08-0YA0), SINAMICS S/G Control Unit w. PROFINET, SIPLUS ET 200MP IM 155-5 PN HF (6AG1155-5AA00-2AC0), SIPLUS ET 200MP IM 155-5 PN HF (6AG1155-5AA00-7AC0), SIPLUS ET 200MP IM 155-5 PN HF T1 RAIL (6AG2155-5AA00-1AC0), SIPLUS ET 200S IM 151-8 PN/DP CPU (6AG1151-8AB01-7AB0), SIPLUS ET 200S IM 151-8F PN/DP CPU (6AG1151-8FB01-2AB0), SIPLUS ET 200SP IM 155-6 PN HF (6AG1155-6AU00-2CN0), SIPLUS ET 200SP IM 155-6 PN HF (6AG1155-6AU00-4CN0), SIPLUS ET 200SP IM 155-6 PN HF (6AG1155-6AU01-2CN0), SIPLUS ET 200SP IM 155-6 PN HF (6AG1155-6AU01-7CN0), SIPLUS ET 200SP IM 155-6 PN HF T1 RAIL (6AG2155-6AU00-1CN0), SIPLUS ET 200SP IM 155-6 PN HF T1 RAIL (6AG2155-6AU01-1CN0), SIPLUS ET 200SP IM 155-6 PN HF TX RAIL (6AG2155-6AU01-4CN0), SIPLUS NET PN/PN Coupler (6AG2158-3AD10-4XA0), SIPLUS S7-300 CPU 314C-2 PN/DP (6AG1314-6EH04-7AB0), SIPLUS S7-300 CPU 315-2 PN/DP (6AG1315-2EH14-7AB0), SIPLUS S7-300 CPU 315F-2 PN/DP (6AG1315-2FJ14-2AB0), SIPLUS S7-300 CPU 317-2 PN/DP (6AG1317-2EK14-7AB0), SIPLUS S7-300 CPU 317F-2 PN/DP (6AG1317-2FK14-2AB0). The Interniche-based TCP Stack can be forced to make very expensive calls for every incoming packet which can lead to a denial of service.

Assessing the Risk of CVE-2019-19300

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2019-19300 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-19300, 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-19300, 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-19300 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2019-19300 poses no threat to data integrity.
  • Availability: High
    CVE-2019-19300 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.116% (probability of exploit)

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

CVE-2019-19300 References

External References

CWE Common Weakness Enumeration

CWE-400

CAPEC Common Attack Pattern Enumeration and Classification

  • XML Ping of the Death CAPEC-147 An attacker initiates a resource depletion attack where a large number of small XML messages are delivered at a sufficiently rapid rate to cause a denial of service or crash of the target. Transactions such as repetitive SOAP transactions can deplete resources faster than a simple flooding attack because of the additional resources used by the SOAP protocol and the resources necessary to process SOAP messages. The transactions used are immaterial as long as they cause resource utilization on the target. In other words, this is a normal flooding attack augmented by using messages that will require extra processing on the target.
  • Sustained Client Engagement CAPEC-227 An adversary attempts to deny legitimate users access to a resource by continually engaging a specific resource in an attempt to keep the resource tied up as long as possible. The adversary's primary goal is not to crash or flood the target, which would alert defenders; rather it is to repeatedly perform actions or abuse algorithmic flaws such that a given resource is tied up and not available to a legitimate user. By carefully crafting a requests that keep the resource engaged through what is seemingly benign requests, legitimate users are limited or completely denied access to the resource.
  • Regular Expression Exponential Blowup CAPEC-492 An adversary may execute an attack on a program that uses a poor Regular Expression(Regex) implementation by choosing input that results in an extreme situation for the Regex. A typical extreme situation operates at exponential time compared to the input size. This is due to most implementations using a Nondeterministic Finite Automaton(NFA) state machine to be built by the Regex algorithm since NFA allows backtracking and thus more complex regular expressions.

Vulnerable Configurations

  • cpe:2.3:h:siemens:ktk_ate530s:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:ktk_ate530s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:ktk_ate530s_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:ktk_ate530s_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:sidoor_atd430w:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:sidoor_atd430w:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:sidoor_atd430w_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:sidoor_atd430w_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:sidoor_ate530s_coated:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:sidoor_ate530s_coated:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:sidoor_ate530s_coated_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:sidoor_ate530s_coated_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:sidoor_ate531s:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:sidoor_ate531s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:sidoor_ate531s_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:sidoor_ate531s_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et_200sp_open_controller_cpu_1515sp_pc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et_200sp_open_controller_cpu_1515sp_pc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_et_200sp_open_controller_cpu_1515sp_pc:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_et_200sp_open_controller_cpu_1515sp_pc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et_200sp_open_controller_cpu_1515sp_pc2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et_200sp_open_controller_cpu_1515sp_pc2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_et_200sp_open_controller_cpu_1515sp_pc2:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_et_200sp_open_controller_cpu_1515sp_pc2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et200mp_im155-5_pn_hf_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et200mp_im155-5_pn_hf_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et200mp_im155-5_pn_hf_firmware:4.2:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et200mp_im155-5_pn_hf_firmware:4.2:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_et200mp_im155-5_pn_hf:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_et200mp_im155-5_pn_hf:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_et200sp_im155-6_mf_hf:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_et200sp_im155-6_mf_hf:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et200sp_im155-6_mf_hf_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et200sp_im155-6_mf_hf_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn_ha_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn_ha_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_et200sp_im155-6_pn_ha:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_et200sp_im155-6_pn_ha:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_et200sp_im155-6_pn_hf:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_et200sp_im155-6_pn_hf:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn_hf_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn_hf_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn_hf_firmware:3.3.1:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn_hf_firmware:3.3.1:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn_hf_firmware:4.2:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn_hf_firmware:4.2:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_et200sp_im155-6_pn\/2_hf:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_et200sp_im155-6_pn\/2_hf:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn\/2_hf_firmware:4.2:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_et200sp_im155-6_pn\/2_hf_firmware:4.2:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_micro-drive_pdc:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_micro-drive_pdc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_micro-drive_pdc_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_micro-drive_pdc_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_pn\/pn_coupler:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_pn\/pn_coupler:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_pn\/pn_coupler_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_pn\/pn_coupler_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_pn\/pn_coupler_firmware:4.2:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_pn\/pn_coupler_firmware:4.2:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1511-1_pn:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1511-1_pn:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1511-1_pn_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1511-1_pn_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1513-1_pn:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1513-1_pn:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1513-1_pn_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1513-1_pn_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1515-2_pn:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1515-2_pn:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1515-2_pn_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1515-2_pn_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1516-3_pn\/dp:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1516-3_pn\/dp:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1516-3_pn\/dp_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1516-3_pn\/dp_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1517-3_pn\/dp:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1517-3_pn\/dp:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1517-3_pn\/dp_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1517-3_pn\/dp_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1518-4_pn\/dp:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1518-4_pn\/dp:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1518-4_pn\/dp_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1518-4_pn\/dp_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1511f-1_pn:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1511f-1_pn:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1511f-1_pn_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1511f-1_pn_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1513f-1_pn_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1513f-1_pn_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1513f-1_pn:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1513f-1_pn:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1515f-2_pn_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1515f-2_pn_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1515f-2_pn:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1515f-2_pn:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1516f-3_pn\/dp_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1516f-3_pn\/dp_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1516f-3_pn\/dp:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1516f-3_pn\/dp:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1517f-3_pn\/dp_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1517f-3_pn\/dp_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1517f-3_pn\/dp:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1517f-3_pn\/dp:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-1500_cpu_1518f-4_pn\/dp_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-1500_cpu_1518f-4_pn\/dp_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-1500_cpu_1518f-4_pn\/dp:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-1500_cpu_1518f-4_pn\/dp:-:*:*:*:*:*:*:*
  • cpe:2.3:a:siemens:simatic_s7-1500:-:*:*:*:*:*:*:*
    cpe:2.3:a:siemens:simatic_s7-1500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-300_cpu_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-300_cpu_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-300_cpu:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-300_cpu:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-400_pn\/dp_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-400_pn\/dp_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-400_pn\/dp:v7:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-400_pn\/dp:v7:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_s7-410_cpu_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_s7-410_cpu_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_s7-410_cpu:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_s7-410_cpu:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_tdc_cp51m1_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_tdc_cp51m1_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_tdc_cp51m1:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_tdc_cp51m1:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_tdc_cpu555_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_tdc_cpu555_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_tdc_cpu555:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_tdc_cpu555:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:simatic_winac_rtx_\(f\)_2010_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:simatic_winac_rtx_\(f\)_2010_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:simatic_winac_rtx_\(f\)_2010:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:simatic_winac_rtx_\(f\)_2010:-:*:*:*:*:*:*:*
  • cpe:2.3:o:siemens:sinamics_s\/g_control_unit_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:siemens:sinamics_s\/g_control_unit_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:siemens:sinamics_s\/g_control_unit:-:*:*:*:*:*:*:*
    cpe:2.3:h:siemens:sinamics_s\/g_control_unit:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-19300: 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...