Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-65m9-m259-7jqw

GHSA-65m9-m259-7jqw is a security vulnerability in react-oauth-flow. O3 Security confirms whether GHSA-65m9-m259-7jqw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Authorization in react-oauth-flow

Published
Sep 3, 2020
Updated
Oct 4, 2021
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Oct 4, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦react-oauth-flow

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

All versions of react-oauth-flow fail to properly implement the OAuth protocol. The package stores secrets in the front-end code. Instead of using a public OAuth client, it uses a confidential client on the browser. This may allow attackers to compromise server credentials.

Recommendation

No fix is currently available. Consider using an alternative module until a fix is made available.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmreact-oauth-flow0.0.0No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-oauth-flow. 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.

  2. Remediation status

    No patched version of react-oauth-flow has shipped for GHSA-65m9-m259-7jqw yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-65m9-m259-7jqw 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-65m9-m259-7jqw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

All versions of `react-oauth-flow` fail to properly implement the OAuth protocol. The package stores secrets in the front-end code. Instead of using a public OAuth client, it uses a confidential client on the browser. This may allow attackers to compromise server credentials. ## Recommendation No fix is currently available. Consider using an alternative module until a fix is made available.
O3 Security · Impact-Aware SCA

Is GHSA-65m9-m259-7jqw in your dependencies?

O3 detects GHSA-65m9-m259-7jqw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-65m9-m259-7jqw: Improper… | O3 Security