# CVE-2019-18245: Path traversal in Reliable Controls LicenseManager

> Authenticated users can insert malicious code into the system root path, enabling execution with elevated privileges in Reliable Controls LicenseManager.

- **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:** 11 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g223-vgj2-7g9m

## What is CVE-2019-18245?

CVE-2019-18245 is a high-severity path traversal vulnerability in Reliable Controls LicenseManager, published on 11 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Reliable Controls LicenseManager versions 3.4 and prior may allow an authenticated user to insert malicious code into the system root path, which may allow execution of code with elevated privileges of the application.

Weakness: CWE-428 (Unquoted Search Path or Element)

## Which versions are affected by CVE-2019-18245?

It affects 1 product.


Products: Reliablecontrols Rc-Licensemanager.

## How do I fix CVE-2019-18245?

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

## Is CVE-2019-18245 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18245 and fix it if it is affected.

What it is: CVE-2019-18245 is a high-severity path traversal vulnerability in Reliable Controls LicenseManager, published on 11 Dec 2019. 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-2019-18245 in the wild and no public exploit code.

Affected product: Reliable Controls LicenseManager. 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-2019-18245/ (Markdown: https://insights.sbomify.com/CVE-2019-18245/index.md)
```

## Sources

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

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