Skip to content
Fencer Intel
critical —

GHSA-433w-mm6h-rv9p json

Auth bypass in SAML provider

published 5y ago modified 5y ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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 you have any questions or comments about this advisory: * Open an issue in [gotrue](https://github.com/netlify/gotrue/issues) * Email us at [security@netlify.com](mailto:security@netlify.com)

Patch / fix

  • go github.com/netlify/gotrue 1.0.0

Is GHSA-433w-mm6h-rv9p in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/netlify/gotrue
<1.0.0
1.0.0

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.