# CVE-2018-5313: Privilege escalation in n/a

> Local attackers can escalate privileges to Administrator or SYSTEM due to weak file permissions set during Rapid SCADA installation.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 8 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v7m7-pch9-8937

## What is CVE-2018-5313?

CVE-2018-5313 is a high-severity vulnerability in n/a, published on 8 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability allows local attackers to escalate privilege on Rapid Scada 5.5.0 because of weak C:\SCADA permissions. The specific flaw exists within the access control that is set and modified during the installation of the product. The product sets weak access control restrictions. An attacker can leverage this vulnerability to execute arbitrary code under the context of Administrator, the IUSR account, or SYSTEM.

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

## Which versions are affected by CVE-2018-5313?

It affects 1 product.


Products: Rapidscada Rapid Scada.

## How do I fix CVE-2018-5313?

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

## Is CVE-2018-5313 being exploited?

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

## Other vulnerabilities in n/a

- [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-2024-22016](https://insights.sbomify.com/CVE-2024-22016/): Incorrect Permission Assignment for Critical Resource in Rapid SCADA (high 7.8)
- [CVE-2020-22722](https://insights.sbomify.com/CVE-2020-22722/): 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-2018-5313 and fix it if it is affected.

What it is: CVE-2018-5313 is a high-severity vulnerability in n/a, published on 8 Mar 2018. 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-2018-5313 in the wild and no public exploit code.

Affected product: n/a. 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-2018-5313/ (Markdown: https://insights.sbomify.com/CVE-2018-5313/index.md)
```

## Sources

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

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