# CVE-2019-10995: Hardcoded credentials in ABB CP651 HMI products

> Hidden administrative accounts in ABB CP651 HMIs allow attackers to gain unauthorized privileged access to the interface.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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:** 14 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6qrc-v8hx-x5f6

## What is CVE-2019-10995?

CVE-2019-10995 is a high-severity vulnerability in ABB CP651 HMI products, published on 14 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ABB CP651 HMI products revision BSP UN30 v1.76 and prior implement hidden administrative accounts that are used during the provisioning phase of the HMI interface.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 8 products.


Products: Abb Cp651-Web Firmware, Abb Cp651 Firmware, Abb Cp661-Web Firmware, Abb Cp661 Firmware, Abb Cp665-Web Firmware, Abb Cp665 Firmware, Abb Cp676-Web Firmware, Abb Cp676 Firmware.

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

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

## Is CVE-2019-10995 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10995 is a high-severity vulnerability in ABB CP651 HMI products, published on 14 Jan 2020. 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-10995 in the wild and no public exploit code.

Affected product: ABB CP651 HMI products. 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-10995/ (Markdown: https://insights.sbomify.com/CVE-2019-10995/index.md)
```

## Sources

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

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