How severe is GHSA-g3qw-9pgp-xpj4?

No CVSS score has been assigned to GHSA-g3qw-9pgp-xpj4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g3qw-9pgp-xpj4?

GHSA-g3qw-9pgp-xpj4 affects the following packages: njwt (npm). Ecosystems affected: npm.

How do I fix GHSA-g3qw-9pgp-xpj4?

Update njwt to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3qw-9pgp-xpj4 is resolved across your whole dependency graph.

How do I detect GHSA-g3qw-9pgp-xpj4 in my npm dependencies?

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

How do I mitigate GHSA-g3qw-9pgp-xpj4 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-g3qw-9pgp-xpj4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g3qw-9pgp-xpj4 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-g3qw-9pgp-xpj4 published, and has it been updated?

GHSA-g3qw-9pgp-xpj4 was published on September 1, 2020 and was last updated on August 31, 2020. 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

Out-of-bounds Read in njwtGHSA-g3qw-9pgp-xpj4

GHSA-g3qw-9pgp-xpj4 is a security vulnerability in njwt. A fix is available for njwt — see the affected versions and patch details below.

Published

Sep 1, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦njwt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Versions of njwt prior to 1.0.0 are vulnerable to out-of-bounds reads when a number is passed into the base64urlEncode function.

On Node.js 6.x or lower this can expose sensitive information and on any other version of Node.js this creates a Denial of Service vulnerability.

Recommendation

Upgrade to version 1.0.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`njwt`	all versions	1.0.0`npm install njwt@1.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for njwt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update njwt to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3qw-9pgp-xpj4 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Versions of `njwt` prior to 1.0.0 are vulnerable to out-of-bounds reads when a number is passed into the `base64urlEncode` function. On Node.js 6.x or lower this can expose sensitive information and on any other version of Node.js this creates a Denial of Service vulnerability. ## Recommendation Upgrade to version 1.0.0.

O3 Security · Impact-Aware SCA

Is GHSA-g3qw-9pgp-xpj4 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works