GHSA-wpfr-6297-9v57 json
User object created with invalid provider data in GoTrue
published 4y ago modified 8mo ago also GO-2022-0365
- 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 _What kind of vulnerability is it? Who is impacted?_
Under certain circumstances a valid user object would have been created with invalid provider metadata.
This vulnerability affects everyone running an instance of GoTrue as a service. We advise you to update especially if you are using the provider metadata from the user object to secure other resources.
### Patches _Has the problem been patched? What versions should users upgrade to?_
A patch is available with the release of version [1.0.1 on Github](https://github.com/netlify/gotrue/releases/tag/v1.0.1).
### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_
If you don't rely on the provider metadata in the user object, you might not be affected. We still strongly recommend upgrading.
### References _Are there any links users can visit to find out more?_
This problem was initially found and reported by the team at Supabase: https://github.com/supabase/gotrue/security/advisories/GHSA-5hvv-9cqv-894r. We want to thank them for the cooperation around this report.
In contrast to their advisory, we decided to set the severity to "Moderate" since the provider metadata is not an inherent security feature of this GoTrue codebase or the Netlify ecosystem.
### For more information If you have any questions or comments about this advisory: * Email us at [security@netlify.com](mailto:security@netlify.com)
Patch / fix
- go github.com/netlify/gotrue 1.0.1
- github.com/netlify/gotrue@4d8a3b3 commit
- github.com/netlify/gotrue#313 pull request
- github.com/netlify/gotrue/releases/tag/v1.0.1 release
Is GHSA-wpfr-6297-9v57 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/netlify/gotrue | <1.0.1 |
1.0.1 |
References
Sources
- GitHub Advisory GHSA-wpfr-6297-9v57
- OSV GO-2022-0365
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.