Description
If an attacker can successfully authenticate through SSO/Access Code, they can obtain the real backend API Key by modifying the base URL to their own attack URL on the frontend and setting up a server-side request.
Recommendation
Update the @lobehub/chat package to the latest compatible version. Followings are version details:
- Affected version(s): < 0.162.25
- Patched version(s): 0.162.25
References
Could your website be exposed too?
SmartScanner can check your website for Lobe Chat API Key Leak and gives you actionable findings to investigate.
Start a free scanRelated Issues
- lobe-chat `/api/proxy` endpoint Server-Side Request Forgery vulnerability - CVE-2024-32964
- lobe-chat implemented an insufficient fix for GHSA-mxhq-xw3g-rphc (CVE-2024-32964) - CVE-2024-47066
- @lobehub/chat vulnerable to unauthorized access to plugins - CVE-2024-24566
- @lobehub/chat Server Side Request Forgery vulnerability - CVE-2024-32965
You might also like:
See something that needs correcting? Let us knowUpdated June 17, 2024