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

Auth bypass in SAML providerGHSA-433w-mm6h-rv9p

GHSA-433w-mm6h-rv9p is a security vulnerability in github.com/netlify/gotrue. A fix is available for github.com/netlify/gotrue — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of May 21, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/netlify/gotrue

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

Description

Impact

The following vulnerabilities have been disclosed, which impact users leveraging the SAML auth provider:

Patches

Patch available

Please upgrade to v1.0.0 or commit hash a2b4dd6bc4ef7562d1df044098b303f564eefa90

Workarounds

No known workarounds.

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/netlify/gotrueall versions1.0.0go get github.com/netlify/gotrue@v1.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update github.com/netlify/gotrue to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-433w-mm6h-rv9p is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact The following vulnerabilities have been disclosed, which impact users leveraging the SAML auth provider: - [`goxmldsig` - Signature Validation Bypass](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) - [`gosaml2` - Authentication Bypass](https://github.com/russellhaering/gosaml2/security/advisories/GHSA-xhqq-x44f-9fgg) ### Patches [Patch available](https://github.com/netlify/gotrue/pull/274) Please upgrade to v1.0.0 or commit hash `a2b4dd6bc4ef7562d1df044098b303f564eefa90` ### Workarounds No known workarounds. ### For more information If y
O3 Security · Impact-Aware SCA

Is GHSA-433w-mm6h-rv9p in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Auth bypass in SAML provider