How severe is GHSA-xmh9-rg6f-j3mr?

No CVSS score has been assigned to GHSA-xmh9-rg6f-j3mr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xmh9-rg6f-j3mr?

GHSA-xmh9-rg6f-j3mr affects the following packages: @solid/identity-token-verifier (npm). Ecosystems affected: npm.

How do I fix GHSA-xmh9-rg6f-j3mr?

Update @solid/identity-token-verifier to 0.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xmh9-rg6f-j3mr is resolved across your whole dependency graph.

How do I detect GHSA-xmh9-rg6f-j3mr in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @solid/identity-token-verifier, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xmh9-rg6f-j3mr if there is no patch (or I can't update yet)?

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.

Is GHSA-xmh9-rg6f-j3mr actively exploited in the wild?

No public exploit code has been indexed for GHSA-xmh9-rg6f-j3mr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-xmh9-rg6f-j3mr published, and has it been updated?

GHSA-xmh9-rg6f-j3mr was published on March 12, 2021 and was last updated on March 10, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Verification flaw in Solid identity-token-verifierGHSA-xmh9-rg6f-j3mr

Fix: solid/identity-token-verifier@fbdeb4a

GHSA-xmh9-rg6f-j3mr is a security vulnerability in @solid/identity-token-verifier. A fix is available for @solid/identity-token-verifier — see the affected versions and patch details below.

Published

Mar 12, 2021

Updated

Mar 10, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 10, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@solid/identity-token-verifiernpm

127downloads / week

Description

Impact

Severity

Any Pod on a Solid server using a vulnerable version of the identity-token-verifier library is at risk of a spoofed Demonstration of Proof-of-Possession (DPoP) token binding. This vulnerability could give total and complete access to a targeted Pod.

Summary

A verification flaw in the implementation of the identity token verifier library (https://github.com/solid/identity-token-verifier) allows DPoP proofs to be spoofed.

DPoP proofs are used to bind access tokens to a private key meant to be in sole possession of a specific user. Instead of verifying against the hash of an embedded public key, the library instead verifies against a field that an attacker can modify to spoof another user’s DPoP.

A stolen DPoP proof, when used in the right context, therefore allows the rebinding of a DPoP-bound access token. Any attacker in possession of a targeted access token could build an attack environment to replay it on any Pod service with this vulnerability.

Patches

A new version 0.5.2 of identity-token-verifier fixes the verification: https://github.com/solid/identity-token-verifier/blob/7e18d86d65ee681e8ae912b6a032a1bae3cae570/src/lib/DPoP.ts#L25-L35

Workarounds

None

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

Open an issue in the identity-token-verifier repository.
Email: [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@solid/identity-token-verifier`	all versions	0.5.2`npm install @solid/identity-token-verifier@0.5.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @solid/identity-token-verifier, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @solid/identity-token-verifier to 0.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xmh9-rg6f-j3mr 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.

Frequently Asked Questions

### Impact #### Severity Any Pod on a Solid server using a vulnerable version of the identity-token-verifier library is at risk of a spoofed Demonstration of Proof-of-Possession (DPoP) token binding. This vulnerability could give total and complete access to a targeted Pod. #### Summary A verification flaw in the implementation of the identity token verifier library (https://github.com/solid/identity-token-verifier) allows DPoP proofs to be spoofed. DPoP proofs are used to bind access tokens to a private key meant to be in sole possession of a specific user. Instead of verifying against the

O3 Security · Impact-Aware SCA

Is GHSA-xmh9-rg6f-j3mr in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works