Firmware upload verification bypass in TXpert Hub CoreTec 4

published 2022-06-07 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-22168

cvss: 6.7; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits: 0; none known

A vulnerability exists in the file upload validation part of Hitachi Energy TXpert Hub CoreTec 4 product. The vulnerability allows an attacker or malicious agent who manages to gain access to the system and obtain an account with sufficient privilege to upload a malicious firmware to the product. This issue affects: Hitachi Energy TXpert Hub CoreTec 4 version 2.0.0; 2.0.1; 2.1.0; 2.1.1; 2.1.2; 2.1.3; 2.2.0; 2.2.1.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-249-04 updated 2022-09-06 cvss 6.0

Hitachi Energy TXpert Hub CoreTec 4

Hitachi Energy TXpert Hub CoreTec 4 2.2.0, 2.2.1, 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.1.3
affected: vendor fix, mitigation “Physically protect process control systems from unauthorized direct access.” search.abb.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.7	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.2	AV:L/AC:L/Au:N/C:C/I:C/A:C

Affected products

Hitachi Energy TXpert Hub CoreTec 4 version

Classification

Weakness

CWE-494 Download of Code Without Integrity Check
CWE-434 Unrestricted Upload of File with Dangerous Type

References

search.abb.com /library/Download.aspx?DocumentID=8DBD000080&LanguageCode=en&DocumentPartId=&Action=Launch&utm_campaign=&utm_c
vendor-advisory

Sources

CVE List CVE-2021-35532
NVD CVE-2021-35532

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary