# CVE-2024-22016: Incorrect Permission Assignment for Critical Resource in Rapid SCADA

> An authorized user can write to the Scada directory, potentially leading to privilege escalation in Rapid SCADA.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2024
- **Updated:** 8 Nov 2024
- **Also known as:** GHSA-2rrv-22x6-4f23

## What is CVE-2024-22016?

CVE-2024-22016 is a high-severity vulnerability in Rapid SCADA, published on 1 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Rapid Software LLC's Rapid SCADA versions prior to Version 5.8.4, an authorized user can write directly to the Scada directory. This may allow privilege escalation.

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

## Which versions are affected by CVE-2024-22016?

It affects 1 product.


Products: Rapidscada Rapid Scada.

## How do I fix CVE-2024-22016?

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

## Is CVE-2024-22016 being exploited?

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

## Other vulnerabilities in Rapid SCADA

- [CVE-2024-21764](https://insights.sbomify.com/CVE-2024-21764/): Use of Hard-Coded Credentials in Rapid SCADA (critical 9.8)
- [CVE-2024-21852](https://insights.sbomify.com/CVE-2024-21852/): Rapid SCADA Path Traversal (high 8.8)
- [CVE-2020-22722](https://insights.sbomify.com/CVE-2020-22722/): Privilege escalation in n/a (high 7.8)
- [CVE-2018-5313](https://insights.sbomify.com/CVE-2018-5313/): Privilege escalation in n/a (high 7.8)
- [CVE-2024-47221](https://insights.sbomify.com/CVE-2024-47221/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22016 and fix it if it is affected.

What it is: CVE-2024-22016 is a high-severity vulnerability in Rapid SCADA, published on 1 Feb 2024. 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-2024-22016 in the wild and no public exploit code.

Affected product: Rapid SCADA. 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-2024-22016/ (Markdown: https://insights.sbomify.com/CVE-2024-22016/index.md)
```

## Sources

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

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