How severe is GHSA-h6mp-mc7g-mg49?

GHSA-h6mp-mc7g-mg49 has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-h6mp-mc7g-mg49?

GHSA-h6mp-mc7g-mg49 affects the following packages: scheb/two-factor-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-h6mp-mc7g-mg49?

Update scheb/two-factor-bundle to 3.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h6mp-mc7g-mg49 is resolved across your whole dependency graph.

How do I detect GHSA-h6mp-mc7g-mg49 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for scheb/two-factor-bundle. 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-h6mp-mc7g-mg49 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-h6mp-mc7g-mg49?

O3 pinpoints whether GHSA-h6mp-mc7g-mg49 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-h6mp-mc7g-mg49 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h6mp-mc7g-mg49 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-h6mp-mc7g-mg49 published, and has it been updated?

GHSA-h6mp-mc7g-mg49 was published on May 21, 2024 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-h6mp-mc7g-mg49

HIGH

scheb/two-factor-bundle bypass two-factor authentication with unverified JWT trusted device token

Published

May 21, 2024

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘scheb/two-factor-bundle

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

Description

Before version 3.7 the bundle is vulnerable to a security issue in JWT, which can be exploited by an attacker to generate trusted device cookies on their own, effectively by-passing two-factor authentication.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`scheb/two-factor-bundle`	≥ 3.0.0&&< 3.7.0	3.7.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for scheb/two-factor-bundle. 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 scheb/two-factor-bundle to 3.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h6mp-mc7g-mg49 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-h6mp-mc7g-mg49 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-h6mp-mc7g-mg49. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Before version 3.7 the bundle is vulnerable to a [security issue in JWT](https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/), which can be exploited by an attacker to generate trusted device cookies on their own, effectively by-passing two-factor authentication.

O3 Security · Impact-Aware SCA

Is GHSA-h6mp-mc7g-mg49 in your dependencies?

O3 detects GHSA-h6mp-mc7g-mg49 across Packagist 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