GHSA-ff5x-w9wg-h275
Fix: rabobank-blockchain/vp-toolkit@18a7db8GHSA-ff5x-w9wg-h275 is a security vulnerability in vp-toolkit. O3 Security confirms whether GHSA-ff5x-w9wg-h275 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Holder can generate proof of ownership for credentials it does not control in vp-toolkit
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.
vp-toolkitnpmDescription
Impact
The verifyVerifiablePresentation() method check the cryptographic integrity of the Verifiable Presentation, but it does not check if the credentialSubject.id DID matches the signer of the VP proof.
The verifier is impacted by this vulnerability.
Patches
Patch will be available in version 0.2.2.
Workarounds
- Compute the address out of the
verifiablePresentation.proof.n.verificationMethodusinggetAddressFromPubKey()from[email protected]and match it with thecredentialSubject.idaddress from the credential.
References
For more information
If you have any questions or comments about this advisory:
- Discuss in the existing issue
- Contact me
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | vp-toolkit | all versions | 0.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vp-toolkit. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update vp-toolkit to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ff5x-w9wg-h275 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.
How O3 protects you
O3 pinpoints whether GHSA-ff5x-w9wg-h275 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-ff5x-w9wg-h275. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-ff5x-w9wg-h275 in your dependencies?
O3 detects GHSA-ff5x-w9wg-h275 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.