{"answers":{"affected":"2 open source packages ship an affected version, including vp-toolkit.","exploited":"There is no known exploitation of GHSA-ff5x-w9wg-h275 in the wild and no public exploit code.","fix":"Upgrade vp-toolkit to 0.2.2 or later.","what":"GHSA-ff5x-w9wg-h275 is an authentication bypass vulnerability in vp-toolkit, published on 6 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-ff5x-w9wg-h275 and fix it if it is affected.\n\nWhat it is: GHSA-ff5x-w9wg-h275 is an authentication bypass vulnerability in vp-toolkit, published on 6 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-ff5x-w9wg-h275 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vp-toolkit (npm): affected all versions; fixed in 0.2.2\n- vp-toolkit (npm): affected all versions; fixed in 0.2.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-ff5x-w9wg-h275/ (Markdown: https://insights.sbomify.com/GHSA-ff5x-w9wg-h275/index.md)","id":"GHSA-ff5x-w9wg-h275","markdown":"https://insights.sbomify.com/GHSA-ff5x-w9wg-h275/index.md","name":"GHSA-ff5x-w9wg-h275","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Verifiable Presentation library","requires_auth":"none","summary":"Attackers can forge ownership proofs for credentials they do not control, bypassing verification checks in the vp-toolkit library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nThe [`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.\n\nThe **verifier** is impacted by this vulnerability.\n\n### Patches\nPatch will be available in version 0.2.2.\n\n### Workarounds\n- Compute the address out of the `verifiablePresentation.proof.n.verificationMethod` using `getAddressFromPubKey()` from `crypt-util@0.1.5` and match it with the `credentialSubject.id` address from the credential.\n\n### References\n[Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Discuss in the existing [issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14)\n* [Contact me](https://github.com/rabomarnix)","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Holder can generate proof of ownership for credentials it does not control in vp-toolkit","id":"GHSA-ff5x-w9wg-h275","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["0.2.2"],"introduced":["0"],"last_affected":[],"package":"vp-toolkit","purl":null,"source":"GHSA-ff5x-w9wg-h275"},{"ecosystem":"npm","fixed":["0.2.2"],"introduced":["0"],"last_affected":[],"package":"vp-toolkit","purl":"pkg:npm/vp-toolkit","source":"GHSA-ff5x-w9wg-h275"}],"products":null,"published":"2020-03-06","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can forge ownership proofs for credentials they do not control, bypassing verification checks in the vp-toolkit library.","url":"https://insights.sbomify.com/GHSA-ff5x-w9wg-h275/"}