# CVE-2021-22278: Certificate verification vulnerability in Update Manager of PCM600 Engineering Tool

> Attackers can bypass certificate validation in the Update Manager to install malicious software on systems running PCM600.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Oct 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m4rm-456c-72hq

## What is CVE-2021-22278?

CVE-2021-22278 is a medium-severity vulnerability in ABB PCM600, published on 28 Oct 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A certificate validation vulnerability in PCM600 Update Manager allows attacker to get unwanted software packages to be installed on computer which has PCM600 installed.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2021-22278?

It affects 1 product.


Products: Abb Update Manager.

## How do I fix CVE-2021-22278?

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

## Is CVE-2021-22278 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22278 and fix it if it is affected.

What it is: CVE-2021-22278 is a medium-severity vulnerability in ABB PCM600, published on 28 Oct 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-22278 in the wild and no public exploit code.

Affected product: ABB PCM600. 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-2021-22278/ (Markdown: https://insights.sbomify.com/CVE-2021-22278/index.md)
```

## Sources

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

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