Holder can generate proof of ownership for credentials it does not control in vp-toolkit
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()fromcrypt-util@0.1.5and 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 software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | vp-toolkit | < 0.2.2 | 0.2.2 |
References
- Weakness (CWE)
-- Platform
- npm
- Package
vp-toolkit- Disclosed
- 06.03.2020
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-ff5x-w9wg-h275 - CC BY 4.0
Vulnerability history: vp-toolkit
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 2
- First → latest
- 03.2020 03.2020
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 2
Disclosures per year
- 2020: 2
- 2021: 0
- 2022: 0
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 0
-
Holder can generate proof of ownership for credentials it does not control in vp-toolkit this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.