# CVE-2024-25728: Information disclosure in n/a

> ExpressVPN Windows client leaks DNS requests to ISP servers when split tunneling is enabled, exposing browsing history to remote attackers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2024
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-vpg2-32g8-56wf

## What is CVE-2024-25728?

CVE-2024-25728 is a high-severity vulnerability in n/a, published on 11 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ExpressVPN before 12.73.0 on Windows, when split tunneling is used, sends DNS requests according to the Windows configuration (e.g., sends them to DNS servers operated by the user's ISP instead of to the ExpressVPN DNS servers), which may allow remote attackers to obtain sensitive information about websites visited by VPN users.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2024-25728?

It affects 1 product.


Products: Expressvpn Expressvpn.

## How do I fix CVE-2024-25728?

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

## Is CVE-2024-25728 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-29238](https://insights.sbomify.com/CVE-2020-29238/): Integer overflow in n/a (high 7.5)
- [CVE-2018-15490](https://insights.sbomify.com/CVE-2018-15490/): Path traversal in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25728 and fix it if it is affected.

What it is: CVE-2024-25728 is a high-severity vulnerability in n/a, published on 11 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-25728 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-2024-25728/ (Markdown: https://insights.sbomify.com/CVE-2024-25728/index.md)
```

## Sources

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

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