# CVE-2019-7229: Supply chain in n/a

> Attackers can inject malicious firmware or software into ABB CP635 HMIs via unencrypted USB or FTP transfers, leading to unauthorized code execution.

- **Severity:** High 8.3 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rrrj-wqph-2cmr

## What is CVE-2019-7229?

CVE-2019-7229 is a high-severity vulnerability in n/a, published on 24 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2019-7229?

It affects 8 products.


Products: Abb Board Support Package Un31, Abb Cp620-Web Firmware, Abb Cp620 Firmware, Abb Cp630-Web Firmware, Abb Cp630 Firmware, Abb Cp635-B Firmware, Abb Cp635-Web Firmware, Abb Cp635 Firmware.

## How do I fix CVE-2019-7229?

No fix has been published for CVE-2019-7229 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-7229 being exploited?

There is no known exploitation of CVE-2019-7229 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7229 and fix it if it is affected.

What it is: CVE-2019-7229 is a high-severity vulnerability in n/a, published on 24 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7229 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-7229/ (Markdown: https://insights.sbomify.com/CVE-2019-7229/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-7229
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-7229
- OSV: https://osv.dev/vulnerability/CVE-2019-7229

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-7229/
Summaries are generated and may contain mistakes; the official description above is the record.