Holder can generate proof of ownership for credentials it does not control in vp-toolkit
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### Impact The [`verifyVerifiablePresentation()`](https://github.com/rabobank-blockchain/vp-toolkit/blob/master/src/service/signers/verifiable-presentation-signer.ts#L97) method check the cryptographic integrity of the Verifiable Presentation, but it does not check if the [`credentialSubject.id`](https://github.com/rabobank-blockchain/vp-toolkit-models/blob/develop/src/model/verifiable-credential.ts#L150) 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.verificationMethod` using `getAddressFromPubKey()` from `[email protected]` and match it with the `credentialSubject.id` address from the credential. ### References [Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14) ### For more information If you have any questions or comments about this advisory: * Discuss in the existing [issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14) * [Contact me](https://github.com/rabomarnix)
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | vp-toolkit (npm) | before 0.2.2 | 0.2.2 | Patch available | GHSA-ff5x-w9wg-h275 |
- vp-toolkit (npm) Vendor— Affected before 0.2.2 Fixed in 0.2.2 Patch available GHSA-ff5x-w9wg-h275
Remediation
- Fix · GHSA-ff5x-w9wg-h275 vp-toolkit (npm) Fixed in 0.2.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-ff5x-w9wg-h275
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences