# CVE-2018-19666: Path traversal in n/a

> Local attackers can exploit directory traversal in the OSSEC Windows agent to gain SYSTEM privileges.

- **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:** 29 Nov 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wq56-87f7-3fcv

## What is CVE-2018-19666?

CVE-2018-19666 is a high-severity path traversal vulnerability in Wazuh Wazuh, published on 29 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The agent in OSSEC through 3.1.0 on Windows allows local users to gain NT AUTHORITY\SYSTEM access via Directory Traversal by leveraging full access to the associated OSSEC server.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 2 products.


Products: Ossec Ossec, Wazuh Wazuh.

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

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

## Is CVE-2018-19666 being exploited?

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

## Other vulnerabilities in Wazuh Wazuh

- [CVE-2020-8443](https://insights.sbomify.com/CVE-2020-8443/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-8444](https://insights.sbomify.com/CVE-2020-8444/): Use after free in n/a (critical 9.8)
- [CVE-2020-8445](https://insights.sbomify.com/CVE-2020-8445/): Other in n/a (critical 9.8)
- [CVE-2020-8447](https://insights.sbomify.com/CVE-2020-8447/): Use after free in n/a (critical 9.8)
- [CVE-2020-8442](https://insights.sbomify.com/CVE-2020-8442/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19666 is a high-severity path traversal vulnerability in Wazuh Wazuh, published on 29 Nov 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-19666 in the wild and no public exploit code.

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

## Sources

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

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