# CVE-2020-8486: ABB System 800xA Inter process communication vulnerability - 800xA RNRP

> An authenticated local attacker can inject data into ABB System 800xA RNRP, disrupting node redundancy handling.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5gf9-wgvj-3pxx

## What is CVE-2020-8486?

CVE-2020-8486 is a medium-severity missing authorization vulnerability in ABB 800xA RNRP, published on 29 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient protection of the inter-process communication functions in ABB System 800xA RNRP (all published versions) enables an attacker authenticated on the local system to inject data, affect node redundancy handling.

Weakness: CWE-264

## Which versions are affected by CVE-2020-8486?

It affects 1 product.


Products: Abb 800xa Rnrp.

## How do I fix CVE-2020-8486?

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

## Is CVE-2020-8486 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8486 and fix it if it is affected.

What it is: CVE-2020-8486 is a medium-severity missing authorization vulnerability in ABB 800xA RNRP, published on 29 Apr 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-2020-8486 in the wild and no public exploit code.

Affected product: ABB 800xA RNRP. 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-2020-8486/ (Markdown: https://insights.sbomify.com/CVE-2020-8486/index.md)
```

## Sources

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

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