# CVE-2019-16930: Information disclosure in n/a

> Attackers can discover the IP address of a Zcash full node owning a shielded address by exploiting exception handling flaws during note plaintext deserialization.

- **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:** 28 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x2rm-rw73-q2w8

## What is CVE-2019-16930?

CVE-2019-16930 is a medium-severity vulnerability in n/a, published on 28 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zcashd in Zcash before 2.0.7-3 allows discovery of the IP address of a full node that owns a shielded address, related to mishandling of exceptions during deserialization of note plaintexts. This affects anyone who has disclosed their zaddr to a third party.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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

It affects 1 product.


Products: Z.cash Zcash.

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

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

## Is CVE-2019-16930 being exploited?

There is no known exploitation of CVE-2019-16930 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-7167](https://insights.sbomify.com/CVE-2019-7167/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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