# CVE-2017-16637: Denial of service in n/a

> Local attackers can cause a crash and process corruption in the VPN client by resetting network data while connected, leading to denial of service.

- **Severity:** Medium 4.4 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/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:** 6 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vw8f-v82q-4wv8

## What is CVE-2017-16637?

CVE-2017-16637 is a medium-severity denial of service vulnerability in n/a, published on 6 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Vectura Perfect Privacy VPN Manager v1.10.10 and v1.10.11, when resetting the network data via the software client, with a running VPN connection, a critical error occurs which leads to a "FrmAdvancedProtection" crash. Although the mechanism malfunctions and an error occurs during the runtime with the stack trace being issued, the software process is not properly terminated. The software client is still attempting to maintain the connection even though the network connection information is being reset live. In that insecure mode, the "FrmAdvancedProtection" component crashes, but the process continues to run with different errors and process corruptions. This local corruption vulnerability can be exploited by local attackers.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-16637?

It affects 1 product.


Products: Perfect-Privacy Vpn Manager.

## How do I fix CVE-2017-16637?

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

## Is CVE-2017-16637 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16637 and fix it if it is affected.

What it is: CVE-2017-16637 is a medium-severity denial of service vulnerability in n/a, published on 6 Nov 2017. 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-2017-16637 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-2017-16637/ (Markdown: https://insights.sbomify.com/CVE-2017-16637/index.md)
```

## Sources

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

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