Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
paulmillr/noble-bls12-381
main @ e02d93f
2
Fixes
0
CVEs
MEDIUM
Peak severity
50.0%
Coverage
Highlights
Cryptographic Issue: 2 prior fixes. Scrutinize any change in this area.
index.ts: most-fixed (2 issues). Treat as high-risk during review.
0 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Cryptographic Issue: Allowing invalid or out-of-bounds elliptic curve points to be processed or serialized without validation can lead to cryptographic failures or invalid signature generation. Ensuring strict point validity is critical to preventing curve attacks.
Cryptographic Issue: Allowing zero as a valid private key compromises cryptographic assumptions and violates current BLS signature specifications. Strict range checks must be applied to all normalized private keys.