GHSA-ff5x-w9wg-h275 Holder can generate proof of ownership for credentials it does not control in vp-toolkit

Not scored Published

Attackers can forge ownership proofs for credentials they do not control, bypassing verification checks in the vp-toolkit library.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is GHSA-ff5x-w9wg-h275?

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.

Official description

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.verificationMethod using getAddressFromPubKey() from [email protected] and match it with the credentialSubject.id address from the credential.

References

Github issue

For more information

If you have any questions or comments about this advisory:

Which versions are affected by GHSA-ff5x-w9wg-h275?

2 open source packages ship an affected version, including vp-toolkit.

PackageAffectedFixed in
vp-toolkit npmAll versions0.2.2
vp-toolkit npmAll versions0.2.2

How do I fix GHSA-ff5x-w9wg-h275?

Upgrade vp-toolkit to 0.2.2 or later.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is GHSA-ff5x-w9wg-h275 being exploited?

There is no known exploitation of GHSA-ff5x-w9wg-h275 in the wild and no public exploit code.

Sources

Is GHSA-ff5x-w9wg-h275 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free