Skip to content
Fencer Intel
high 8.3

CVE-2019-7229 json

The ABB CP635 HMI uses two different transmission methods to upgrade its firmware and its software components: "Utilization of USB/SD Card…

published 7y ago modified 4mo ago also EUVD-2019-16773

cvss
8.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

The ABB CP635 HMI uses two different transmission methods to upgrade its firmware and its software components: "Utilization of USB/SD Card to flash the device" and "Remote provisioning process via ABB Panel Builder 600 over FTP." Neither of these transmission methods implements any form of encryption or authenticity checks against the new firmware HMI software binary files.

Patch / fix

  • abb board_support_package_un31 2.31
  • abb cp620_firmware 2.8.0.424
  • abb cp620-web_firmware 2.8.0.424
  • abb cp630_firmware 2.0.8.424
  • abb cp630-web_firmware 2.8.0.424
  • abb cp635_firmware 2.8.0.424
  • abb cp635-b_firmware 2.8.0.424
  • abb cp635-web_firmware 2.8.0.424

Is CVE-2019-7229 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.10% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • seclists.org http://seclists.org/fulldisclosure/2019/Jun/34 referenced PoC, tagged "exploit" by a source, unverified
  • darkmatter.ae https://www.darkmatter.ae/xen1thlabs/abb-hmi-absence-of-signature-verification-vulnerability-xl-19-005/ referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/153387/ABB-HMI-Missing-Signature-Verification.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.3 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD 2.0 5.4 AV:A/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-494 Download of Code Without Integrity Check

References

Sources

Fencer Intel 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.