# GHSA-fpr5-jp2j-4q2f: paillier-zk has ambiguous challenge derivation

> Ambiguous challenge derivation in paillier-zk non-interactive proofs may allow security bypasses in cryptographic protocols.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jul 2024
- **Also known as:** RUSTSEC-2024-0391

## What is GHSA-fpr5-jp2j-4q2f?

GHSA-fpr5-jp2j-4q2f is a vulnerability in paillier-zk, published on 18 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Challenge derivation in non-interactive ZK proofs was ambiguous and that could lead to security vulnerability (however, it's unknown if it could be exploited).

## Which versions are affected by GHSA-fpr5-jp2j-4q2f?

3 open source packages ship an affected version, including paillier-zk.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `paillier-zk` | crates.io | All versions | 0.4.0 |
| `paillier-zk` | crates.io | All versions | 0.4.0 |
| `paillier-zk` | crates.io | From 0.0.0-0 | 0.4.0 |

## How do I fix GHSA-fpr5-jp2j-4q2f?

Upgrade paillier-zk to 0.4.0 or later.

## Is GHSA-fpr5-jp2j-4q2f being exploited?

There is no known exploitation of GHSA-fpr5-jp2j-4q2f in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-fpr5-jp2j-4q2f and fix it if it is affected.

What it is: GHSA-fpr5-jp2j-4q2f is a vulnerability in paillier-zk, published on 18 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-fpr5-jp2j-4q2f in the wild and no public exploit code.

Affected packages and fixed versions:
- paillier-zk (crates.io): affected all versions; fixed in 0.4.0
- paillier-zk (crates.io): affected all versions; fixed in 0.4.0
- paillier-zk (crates.io): affected from 0.0.0-0; fixed in 0.4.0

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/GHSA-fpr5-jp2j-4q2f/ (Markdown: https://insights.sbomify.com/GHSA-fpr5-jp2j-4q2f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-fpr5-jp2j-4q2f

---
From sbomify Insights: https://insights.sbomify.com/GHSA-fpr5-jp2j-4q2f/
Summaries are generated and may contain mistakes; the official description above is the record.