ecdh vulnerable to Exposure of Resource to Wrong SphereGHSA-p2hp-3wv3-4w74
HIGHFix: developmentil/ecdh#4GHSA-p2hp-3wv3-4w74 is a high-severity (CVSS 7.5) CWE-668 vulnerability in ecdh. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for ecdh — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-p2hp-3wv3-4w74.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
ecdhnpmDescription
In Development IL ecdh before 0.2.0, an attacker can send an invalid point (not on the curve) as the public key, and obtain the derived shared secret.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | ecdh | all versions | 0.2.0npm install ecdh@0.2.0 |
Affected Products
ecdhecdh_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ecdh, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ecdh to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2hp-3wv3-4w74 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-p2hp-3wv3-4w74 in your dependencies?
Find it across npm, including transitive dependencies.