How severe is GHSA-h87q-g2wp-47pj?

No CVSS score has been assigned to GHSA-h87q-g2wp-47pj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h87q-g2wp-47pj?

GHSA-h87q-g2wp-47pj affects the following packages: jsrsasign (npm). Ecosystems affected: npm.

How do I fix GHSA-h87q-g2wp-47pj?

Update jsrsasign to 10.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h87q-g2wp-47pj is resolved across your whole dependency graph.

How do I detect GHSA-h87q-g2wp-47pj in my npm dependencies?

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

How do I mitigate GHSA-h87q-g2wp-47pj 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-h87q-g2wp-47pj actively exploited in the wild?

No public exploit code has been indexed for GHSA-h87q-g2wp-47pj 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-h87q-g2wp-47pj published, and has it been updated?

GHSA-h87q-g2wp-47pj was published on February 9, 2022 and was last updated on February 15, 2022. 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

Signatures are mistakenly recognized to be valid in jsrsasignGHSA-h87q-g2wp-47pj

GHSA-h87q-g2wp-47pj is a security vulnerability in jsrsasign. A fix is available for jsrsasign — see the affected versions and patch details below.

Published

Feb 9, 2022

Updated

Feb 15, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 15, 2022 · 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.

jsrsasignnpm

2.5Mdownloads / week

Description

In the jsrsasign package through 10.1.13 for Node.js, some invalid RSA PKCS#1 v1.5 signatures are mistakenly recognized to be valid. NOTE: there is no known practical attack.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`jsrsasign`	all versions	10.2.0`npm install jsrsasign@10.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jsrsasign, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jsrsasign to 10.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h87q-g2wp-47pj 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

In the jsrsasign package through 10.1.13 for Node.js, some invalid RSA PKCS#1 v1.5 signatures are mistakenly recognized to be valid. NOTE: there is no known practical attack.

O3 Security · Impact-Aware SCA

Is GHSA-h87q-g2wp-47pj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works