References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

Change History

Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.8.0 until 0.11.0, when ENABLE_OAUTH_TOKEN_EXCHANGE=True, /oauth/{provider}/token/exchange accepts a raw provider access token and validates it by calling the provider userinfo endpoint without confirming which OAuth client the token was issued to. Anyone holding an access token minted for any client registered with the same provider could exchange it for an Open WebUI session as that token user, including applications the operator does not control and has never authorized. This issue is fixed in 0.11.0.

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

CWE-287

https://github.com/open-webui/open-webui/commit/b190dcf3caa00dc8b7b9c7312828298d9143f60d

https://github.com/open-webui/open-webui/commit/c4332be71e6e9c314e8a13b9d2819a6932561630

https://github.com/open-webui/open-webui/releases/tag/v0.11.0

https://github.com/open-webui/open-webui/security/advisories/GHSA-rq84-p6rr-vf89

[{"vendor":"open-webui","product":"open-webui","versions":[{"version":">= 0.8.0, < 0.11.0","status":"affected"}]}]