# CVE-2016-7064: Security feature bypass in pritunl-client-electron

> Attackers can bypass signature verification in the Pritunl client to leak sensitive information, requiring users to upgrade to a patched version.

- **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:** 21 Jul 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wc8r-7hj6-v6fg

## What is CVE-2016-7064?

CVE-2016-7064 is a high-severity vulnerability in pritunl-client-electron, published on 21 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in pritunl-client before version 1.0.1116.6. A lack of signature verification leads to sensitive information leakage

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2016-7064?

It affects 1 product.


Products: Pritunl Pritunl-Client.

## How do I fix CVE-2016-7064?

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

## Is CVE-2016-7064 being exploited?

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

## Other vulnerabilities in pritunl-client-electron

- [CVE-2016-7063](https://insights.sbomify.com/CVE-2016-7063/): Path traversal in pritunl-client-electron (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7064 and fix it if it is affected.

What it is: CVE-2016-7064 is a high-severity vulnerability in pritunl-client-electron, published on 21 Jul 2020. 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-2016-7064 in the wild and no public exploit code.

Affected product: pritunl-client-electron. 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-2016-7064/ (Markdown: https://insights.sbomify.com/CVE-2016-7064/index.md)
```

## Sources

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

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