# CVE-2023-48957: Information disclosure in n/a

> PureVPN Linux client fails to route DNS queries through the VPN tunnel, exposing user DNS requests to the ISP.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 25 Aug 2024
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-44pq-qvmw-gj4m

## What is CVE-2023-48957?

CVE-2023-48957 is a medium-severity vulnerability in n/a, published on 25 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PureVPN Linux client 2.0.2-Productions fails to properly handle DNS queries, allowing them to bypass the VPN tunnel and be sent directly to the ISP or default DNS servers.

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

## Which versions are affected by CVE-2023-48957?

It affects 1 product.


Products: Purevpn Purevpn.

## How do I fix CVE-2023-48957?

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

## Is CVE-2023-48957 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-48957 exists.

## Other vulnerabilities in n/a

- [CVE-2018-6822](https://insights.sbomify.com/CVE-2018-6822/): Privilege escalation in n/a (critical 9.8)
- [CVE-2018-10204](https://insights.sbomify.com/CVE-2018-10204/): Privilege escalation in n/a (high 8.8)
- [CVE-2018-18656](https://insights.sbomify.com/CVE-2018-18656/): Hardcoded credentials in n/a (high 7.8)
- [CVE-2018-7484](https://insights.sbomify.com/CVE-2018-7484/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-48957 and fix it if it is affected.

What it is: CVE-2023-48957 is a medium-severity vulnerability in n/a, published on 25 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-48957 exists.

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-2023-48957/ (Markdown: https://insights.sbomify.com/CVE-2023-48957/index.md)
```

## Sources

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

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