LibreChat: Federated OAuth Tokens Exposed via `/api/user` Endpoint
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| LibreChat-AI | LibreChat | affected |
|
No data.
No data.
No data available yet.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.636% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. From 0.8.5 until 0.8.6, GET /api/user in api/server/controllers/UserController.js getUserController serializes federatedTokens and tokenset to the authenticated browser because an earlier response-sanitization fix was not applied to this endpoint. Browser-context script can obtain OAuth access, ID, and refresh credentials that were intended to remain server-side. This issue is fixed in version 0.8.6. | |
| Title | LibreChat: Federated OAuth Tokens Exposed via `/api/user` Endpoint | |
| Weaknesses | CWE-200 CWE-522 |
|
| References |
|
|
| Metrics |
cvssV4_0
|
No data.