# CVE-2019-7167: Other in n/a

> A flaw in Zcash's Sprout zk-SNARK verifier allowed attackers to forge valid proofs for invalid transactions, enabling counterfeiting.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 27 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q567-c5xf-8xjf

## What is CVE-2019-7167?

CVE-2019-7167 is a high-severity vulnerability in n/a, published on 27 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zcash, before the Sapling network upgrade (2018-10-28), had a counterfeiting vulnerability. A key-generation process, during evaluation of polynomials related to a to-be-proven statement, produced certain bypass elements. Availability of these elements allowed a cheating prover to bypass a consistency check, and consequently transform the proof of one statement into an ostensibly valid proof of a different statement, thereby breaking the soundness of the proof system. This misled the original Sprout zk-SNARK verifier into accepting the correctness of a transaction.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2019-7167?

It affects 1 product.


Products: Z.cash Zcash.

## How do I fix CVE-2019-7167?

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

## Is CVE-2019-7167 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-11636](https://insights.sbomify.com/CVE-2019-11636/): Denial of service in n/a (high 7.5)
- [CVE-2019-16930](https://insights.sbomify.com/CVE-2019-16930/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7167 and fix it if it is affected.

What it is: CVE-2019-7167 is a high-severity vulnerability in n/a, published on 27 Mar 2019. 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-2019-7167 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-2019-7167/ (Markdown: https://insights.sbomify.com/CVE-2019-7167/index.md)
```

## Sources

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

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