CyberSecBulletin
CVE-2022-3353NVD status: Modified

FOX61x TEGO1: Improper Resource Shutdown or Release

CVE-2022-3353 is a high-severity improper resource shutdown or release vulnerability in FOX61x TEGO1 from Hitachi Energy, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected FOX61x TEGO1 versions: tego1_r15b08; tego1_r2a16_03; tego1_r2a16, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.1% chance of exploitation within 30 days, higher than 66% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update REB500 to 7.* or 8.*, whichever matches your release line, or a later version.
  2. Update Reb500 Firmware to 8.3.3 or a later version.
  3. Read the advisory on search.abb.com for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Hitachi EnergyFOX61x TEGO1tego1_r15b08; tego1_r2a16_03; tego1_r2a16; tego1_r1e01; tego1_r1d02; tego1_r1c07; tego1_r1b02Not stated
Hitachi EnergyGMS600GMS600 1.3Not stated
Hitachi EnergyITT600 SA ExplorerITT600 SA Explorer 1.1.0; ITT600 SA Explorer 1.1.1; ITT600 SA Explorer 1.1.2; ITT600 SA Explorer 1.5.0; ITT600 SA Explorer 1.5.1; ITT600 SA Explorer 1.6.0; ITT600 SA Explorer 1.6.0.1; ITT600 SA Explorer 1.7.0; and 10 more rangesNot stated
Hitachi EnergyMicroSCADA X SYS600SYS600 10; SYS600 10.1; SYS600 10.1.1; SYS600 10.2; SYS600 10.2.1; SYS600 10.3; SYS600 10.3.1; SYS600 10.4Not stated
Hitachi EnergyMSMMSM 2.2.3;0Not stated
Hitachi EnergyPWC600PWC600 1.0; PWC600 1.1; PWC600 1.2Not stated
Hitachi EnergyREB500REB500 7.0 up to, but not including, 7.*; REB500 8.0 up to, but not including, 8.*7.*, 8.*
Hitachi EnergyRelion® 670Relion 670 1.2; Relion 670 2.0; Relion 670 version 2.1; Relion 670 2.2.0; Relion 670 2.2.1; Relion 670 2.2.2; Relion 670 2.2.3; Relion 670 2.2.4; and 1 more rangesNot stated
Hitachi EnergyRelion® 650Relion 650 1.1; Relion 650 1.3; Relion 650 2.1; Relion 650 2.2.0; Relion 650 2.2.1; Relion 650 2.2.2; Relion 650 2.2.3; Relion 650 2.2.4; and 1 more rangesNot stated
Hitachi EnergySAM600-IORelion SAM600-IO 2.2.1; Relion SAM600-IO 2.2.5Not stated
Hitachi EnergyRTU500RTU500 12.0.1 through 12.0.14; RTU500 12.2.1 through 12.2.11; RTU500 12.4.1 through 12.4.11; RTU500 12.6.1 through 12.6.8; RTU500 12.7.1 through 12.7.4; RTU500 13.2.1 through 13.2.5; RTU500 13.3.1 through 13.3.3; RTU500 13.4.1Not stated
Hitachi EnergyTXpert Hub CoreTec 4CoreTec 4 version 2.0.*; CoreTec 4 version 2.1.*; CoreTec 4 version 2.2.*; CoreTec 4 version 2.3.*; CoreTec 4 version 2.4.*; CoreTec 4 version 3.0.*Not stated
Hitachi EnergyTXpert Hub CoreTec 5CoreTec 5 version 3.0.*Not stated
HitachienergySys600 Firmware10.1 through 10.3.1Not stated
HitachienergyRtu500 Firmware12.0.1.0 through 12.0.14.0; 12.2.1.0 through 12.2.11.0; 12.4.1.0 through 12.4.11.0; 12.6.1.0 through 12.6.8.0; 12.7.1.0 through 12.7.4.0; 13.2.1.0 through 13.2.5.0; 13.3.1 through 13.3.3; 13.4.1Not stated
HitachienergyReb500 Firmware7.0 up to, but not including, 8.3.38.3.3
HitachienergyPwc600 Firmware1.0; 1.1; 1.2Not stated
HitachienergyModular Switchgear Monitoring Firmware2.2.3 and earlierNot stated
HitachienergyRelion Sam600-io Firmware2.2.1; 2.2.5Not stated
HitachienergyRelion 650 Firmware1.1; 1.3; 2.1; 2.2.0; 2.2.1; 2.2.2; 2.2.3; 2.2.4; and 1 more rangesNot stated
HitachienergyRelion 670 Firmware1.2; 2.0; 2.1; 2.2.0; 2.2.1; 2.2.2; 2.2.3; 2.2.4; and 1 more rangesNot stated
HitachienergyGms600 Firmware1.3.0Not stated
HitachienergyFox615 Tego1 Firmwarer1b02; r1c07; r1d02; r1e01; r2b16; r2b16_03; r15b08Not stated
HitachienergyTxpert Hub Coretec 4 Firmware2.0.0 through 3.0.0Not stated
HitachienergyTxpert Hub Coretec 5 Firmware3.0.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.15.9MediumCNA (hitachienergy.com)
CVSS 3.17.5HighNVD

Official description

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:*:*:*:*:*:*:*

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Resource Shutdown or Release

The product does not release or incorrectly releases a resource before it is made available for re-use.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free memory in a function. If you allocate memory that you intend to free upon completion of the function, you must be sure to free the memory at all exit points for that function including error conditions.
  • Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].

More Improper Resource Shutdown or Release vulnerabilities (CWE-404)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Advisories

Recent Improper Resource Shutdown or Release vulnerabilities

Spotted an error? Tell us.