# CVE-2022-1596: ABB Relion REX640 Insufficient file access control

> An authenticated attacker can exploit incorrect file permissions to access the user database and potentially take control of the system node.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xcx4-g33r-wmfq

## What is CVE-2022-1596?

CVE-2022-1596 is a medium-severity missing authorization vulnerability in ABB REX640 PCL1, published on 21 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect Permission Assignment for Critical Resource vulnerability in ABB REX640 PCL1, REX640 PCL2, REX640 PCL3 allows an authenticated attacker to launch an attack against the user database file and try to take control of an affected system node.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2022-1596?

It affects 3 products.


Products: Abb Rex640 Pcl1 Firmware, Abb Rex640 Pcl2 Firmware, Abb Rex640 Pcl3 Firmware.

## How do I fix CVE-2022-1596?

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

## Is CVE-2022-1596 being exploited?

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

## Other vulnerabilities in ABB REX640 PCL1

- [CVE-2023-2876](https://insights.sbomify.com/CVE-2023-2876/): Session cookie exposure for client side script (low 3.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1596 and fix it if it is affected.

What it is: CVE-2022-1596 is a medium-severity missing authorization vulnerability in ABB REX640 PCL1, published on 21 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1596 in the wild and no public exploit code.

Affected product: ABB REX640 PCL1. 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-2022-1596/ (Markdown: https://insights.sbomify.com/CVE-2022-1596/index.md)
```

## Sources

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

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