CVE-2022-3353 Vulnerability Analysis & Exploit Details

CVE-2022-3353
Vulnerability Scoring

5.9
/10
Significant Risk

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

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-2022-3353 Details

Status: Modified

Last updated: 🕖 21 Nov 2024, 07:19 UTC
Originally published on: 🕑 21 Feb 2023, 14:15 UTC

Time between publication and last update: 638 days

CVSS Release: version 3

CVSS3 Source

cybersecurity@hitachienergy.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-3353 Vulnerability Summary

CVE-2022-3353: A vulnerability exists in the IEC 61850 communication stack that affects multiple Hitachi Energy products.  An attacker could exploit the vulnerability by using a specially crafted message sequence, to force the IEC 61850 MMS-server communication stack, to stop accepting new MMS-client connections.  Already existing/established client-server connections are not affected. List of affected CPEs: * cpe:2.3:o:hitachienergy:fox61x_tego1:r15b08:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r2a16_3:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r2a16:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r1e01:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r1d02:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r1c07:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r1b02:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:gms600:1.3.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.1.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.5.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0.1:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.2:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.8.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.4:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.5:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.2:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.2.1:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.3:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.3.1:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.4:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.4.1:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:mms:2.2.3:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:pwc600:1.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:pwc600:1.1:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:pwc600:1.2:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:reb500:7:*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:reb500:8:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion670:1.2.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion670:2.0.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion650:1.1.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion650:1.3.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion650:2.1.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion670:2.1.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relionSAM600-IO:2.2.1:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relionSAM600-IO:2.2.5:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion670:2.2.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion650:2.2.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:rtu500cmu:12.*.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:rtu500cmu:13.*.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:txpert_hub_coretec_4:2.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:txpert_hub_coretec_4:3.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:txpert_hub_coretec_5:3.0:*:*:*:*:*:*:*

Assessing the Risk of CVE-2022-3353

Access Complexity Graph

The exploitability of CVE-2022-3353 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-2022-3353

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

  • Confidentiality: None
    CVE-2022-3353 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2022-3353 poses no threat to data integrity.
  • Availability: High
    CVE-2022-3353 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.93% (probability of exploit)

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

CVE-2022-3353 References

External References

CWE Common Weakness Enumeration

CWE-404

CAPEC Common Attack Pattern Enumeration and Classification

  • Flooding CAPEC-125 An adversary consumes the resources of a target by rapidly engaging in a large number of interactions with the target. This type of attack generally exposes a weakness in rate limiting or flow. When successful this attack prevents legitimate users from accessing the service and can cause the target to crash. This attack differs from resource depletion through leaks or allocations in that the latter attacks do not rely on the volume of requests made to the target but instead focus on manipulation of the target's operations. The key factor in a flooding attack is the number of requests the adversary can make in a given period of time. The greater this number, the more likely an attack is to succeed against a given target.
  • Excessive Allocation CAPEC-130 An adversary causes the target to allocate excessive resources to servicing the attackers' request, thereby reducing the resources available for legitimate services and degrading or denying services. Usually, this attack focuses on memory allocation, but any finite resource on the target could be the attacked, including bandwidth, processing cycles, or other resources. This attack does not attempt to force this allocation through a large number of requests (that would be Resource Depletion through Flooding) but instead uses one or a small number of requests that are carefully formatted to force the target to allocate excessive resources to service this request(s). Often this attack takes advantage of a bug in the target to cause the target to allocate resources vastly beyond what would be needed for a normal request.
  • Resource Leak Exposure CAPEC-131 An adversary utilizes a resource leak on the target to deplete the quantity of the resource available to service legitimate requests.
  • TCP Fragmentation CAPEC-494 An adversary may execute a TCP Fragmentation attack against a target with the intention of avoiding filtering rules of network controls, by attempting to fragment the TCP packet such that the headers flag field is pushed into the second fragment which typically is not filtered.
  • UDP Fragmentation CAPEC-495 An attacker may execute a UDP Fragmentation attack against a target server in an attempt to consume resources such as bandwidth and CPU. IP fragmentation occurs when an IP datagram is larger than the MTU of the route the datagram has to traverse. Typically the attacker will use large UDP packets over 1500 bytes of data which forces fragmentation as ethernet MTU is 1500 bytes. This attack is a variation on a typical UDP flood but it enables more network bandwidth to be consumed with fewer packets. Additionally it has the potential to consume server CPU resources and fill memory buffers associated with the processing and reassembling of fragmented packets.
  • ICMP Fragmentation CAPEC-496 An attacker may execute a ICMP Fragmentation attack against a target with the intention of consuming resources or causing a crash. The attacker crafts a large number of identical fragmented IP packets containing a portion of a fragmented ICMP message. The attacker these sends these messages to a target host which causes the host to become non-responsive. Another vector may be sending a fragmented ICMP message to a target host with incorrect sizes in the header which causes the host to hang.
  • BlueSmacking CAPEC-666 An adversary uses Bluetooth flooding to transfer large packets to Bluetooth enabled devices over the L2CAP protocol with the goal of creating a DoS. This attack must be carried out within close proximity to a Bluetooth enabled device.

Vulnerable Configurations

  • cpe:2.3:h:hitachienergy:sys600:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:sys600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.0.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.0.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.0.13.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.0.13.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.0.14.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.0.14.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.2.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.2.11.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.2.11.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.4.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.4.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.4.11.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.4.11.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.6.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.6.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.6.7.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.6.7.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.6.8.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.6.8.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.7.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.7.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.7.3.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.7.3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:12.7.4.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:12.7.4.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:13.2.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:13.2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:13.2.4.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:13.2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:13.2.5.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:13.2.5.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:13.3.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:13.3.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:13.3.2:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:13.3.2:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:13.3.3:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:13.3.3:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:rtu500_firmware:13.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:rtu500_firmware:13.4.1:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:rtu500:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:rtu500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:reb500_firmware:7.3:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:reb500_firmware:7.3:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:reb500_firmware:7.60.19:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:reb500_firmware:7.60.19:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:reb500_firmware:8.2:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:reb500_firmware:8.2:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:reb500_firmware:8.2.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:reb500_firmware:8.2.0.5:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:reb500_firmware:8.3:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:reb500_firmware:8.3:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:reb500_firmware:8.3.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:reb500_firmware:8.3.1.0:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:reb500:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:reb500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:pwc600_firmware:1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:pwc600_firmware:1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:pwc600_firmware:1.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:pwc600_firmware:1.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:pwc600_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:pwc600_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:pwc600:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:pwc600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:modular_switchgear_monitoring_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:modular_switchgear_monitoring_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:modular_switchgear_monitoring_firmware:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:modular_switchgear_monitoring_firmware:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:modular_switchgear_monitoring_firmware:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:modular_switchgear_monitoring_firmware:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:modular_switchgear_monitoring:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:modular_switchgear_monitoring:-:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_sam600-io_firmware:2.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_sam600-io_firmware:2.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_sam600-io_firmware:2.2.5:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_sam600-io_firmware:2.2.5:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:relion_sam600-io:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:relion_sam600-io:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_650_firmware:1.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_650_firmware:1.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_650_firmware:1.3:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_650_firmware:1.3:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_650_firmware:2.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_650_firmware:2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.2:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.2:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.3:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.4:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.4:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.5:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_650_firmware:2.2.5:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:relion_650:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:relion_650:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_670_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_670_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_670_firmware:2.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_670_firmware:2.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_670_firmware:2.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_670_firmware:2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.2:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.2:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.3:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.4:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.4:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.5:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:relion_670_firmware:2.2.5:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:relion_670:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:relion_670:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:gms600_firmware:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:gms600_firmware:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:gms600:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:gms600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r1b02:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r1b02:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r1c07:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r1c07:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r1d02:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r1d02:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r1e01:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r1e01:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r2b16:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r2b16:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r2b16_03:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r2b16_03:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r15b08:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:fox615_tego1_firmware:r15b08:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:fox615_tego1:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:fox615_tego1:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.1.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.1.1:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.1.2:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.1.2:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.1.3:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.1.3:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:txpert_hub_coretec_4_firmware:2.2.1:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:txpert_hub_coretec_4:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:txpert_hub_coretec_4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hitachienergy:txpert_hub_coretec_5_firmware:3.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:hitachienergy:txpert_hub_coretec_5_firmware:3.0.0:*:*:*:*:*:*:*
  • cpe:2.3:h:hitachienergy:txpert_hub_coretec_5:-:*:*:*:*:*:*:*
    cpe:2.3:h:hitachienergy:txpert_hub_coretec_5:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-3353: 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-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • 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...