paillier-zk has ambiguous challenge derivation

published 2024-07-18 2y ago modified 2025-10-28 last yr. also RUSTSEC-2024-0391

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

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).

Patch / fix

fixed in 1 links 1

crates.io paillier-zk 0.4.0

github.com/dfns/paillier-zk#49 pull request

Is GHSA-fpr5-jp2j-4q2f in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
crates.io	paillier-zk	<0.4.0 >=0.0.0-0, <0.4.0	0.4.0

Classification

Weakness

CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

github.com /dfns/paillier-zk/pull/49
web
github.com /LFDT-Lockness/paillier-zk
package
rustsec.org /advisories/RUSTSEC-2024-0391.html
web, advisory
crates.io /crates/paillier-zk
package

Sources

GitHub Advisory GHSA-fpr5-jp2j-4q2f
OSV RUSTSEC-2024-0391

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.