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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-g3qw-9pgp-xpj4 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.

How does O3 Security protect against GHSA-g3qw-9pgp-xpj4?

O3 pinpoints whether GHSA-g3qw-9pgp-xpj4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-g3qw-9pgp-xpj4

GHSA-g3qw-9pgp-xpj4 is a security vulnerability in njwt. O3 Security confirms whether GHSA-g3qw-9pgp-xpj4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Out-of-bounds Read in njwt

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

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

116other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

njwtnpm

739Kdownloads / week

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for njwt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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.
How O3 protects you
O3 pinpoints whether GHSA-g3qw-9pgp-xpj4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g3qw-9pgp-xpj4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-g3qw-9pgp-xpj4 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works