# CVE-2022-25166: Information disclosure in n/a

> A malicious OpenVPN configuration file can leak the user's Net-NTLMv2 hash to an external server when imported by the AWS VPN Client.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5wg4-7x93-v266

## What is CVE-2022-25166?

CVE-2022-25166 is a medium-severity vulnerability in n/a, published on 14 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Amazon AWS VPN Client 2.0.0. It is possible to include a UNC path in the OpenVPN configuration file when referencing file paths for parameters (such as auth-user-pass). When this file is imported and the client attempts to validate the file path, it performs an open operation on the path and leaks the user's Net-NTLMv2 hash to an external server. This could be exploited by having a user open a crafted malicious ovpn configuration file.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-25166?

It affects 1 product.


Products: Amazon Aws Client Vpn.

## How do I fix CVE-2022-25166?

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

## Is CVE-2022-25166 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-25165](https://insights.sbomify.com/CVE-2022-25165/): Race condition in n/a (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25166 and fix it if it is affected.

What it is: CVE-2022-25166 is a medium-severity vulnerability in n/a, published on 14 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-25166 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-2022-25166/ (Markdown: https://insights.sbomify.com/CVE-2022-25166/index.md)
```

## Sources

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

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