# CVE-2018-19792: Memory corruption in n/a

> Local attackers can cause denial of service or potential code execution via a symlink with a long command name in OpenLiteSpeed.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8jp3-8rhj-499h

## What is CVE-2018-19792?

CVE-2018-19792 is a medium-severity memory corruption vulnerability in n/a, published on 3 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The server in LiteSpeed OpenLiteSpeed before 1.5.0 RC6 allows local users to cause a denial of service (buffer overflow) or possibly have unspecified other impact by creating a symlink through which the openlitespeed program can be invoked with a long command name (involving ../ characters), which is mishandled in the LshttpdMain::getServerRootFromExecutablePath function.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Litespeedtech Openlitespeed.

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

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

## Is CVE-2018-19792 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-5519](https://insights.sbomify.com/CVE-2020-5519/): Path traversal in n/a (critical 9.8)
- [CVE-2022-0073](https://insights.sbomify.com/CVE-2022-0073/): Authenticated Remote Code Execution in OpenLiteSpeed Web Server (high 8.8)
- [CVE-2022-0074](https://insights.sbomify.com/CVE-2022-0074/): Privilege Escalation in OpenLiteSpeed Web Server (high 8.8)
- [CVE-2021-26758](https://insights.sbomify.com/CVE-2021-26758/): Privilege escalation in n/a (high 8.8)
- [CVE-2023-40518](https://insights.sbomify.com/CVE-2023-40518/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19792 and fix it if it is affected.

What it is: CVE-2018-19792 is a medium-severity memory corruption vulnerability in n/a, published on 3 Dec 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-19792 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-19792/ (Markdown: https://insights.sbomify.com/CVE-2018-19792/index.md)
```

## Sources

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

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