lobehub lobe-chat up to 1.19.12 server-side request forgery

Summaryinfo

A vulnerability was found in lobehub lobe-chat up to 1.19.12. It has been rated as critical. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in server-side request forgery. This vulnerability is cataloged as CVE-2024-32965. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical has been found in lobehub lobe-chat up to 1.19.12. This affects an unknown function. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Lobe Chat is an open-source, AI chat framework. Versions of lobe-chat prior to 1.19.13 have an unauthorized ssrf vulnerability. An attacker can construct malicious requests to cause SSRF without logging in, attack intranet services, and leak sensitive information. The jwt token header X-Lobe-Chat-Auth strored proxy address and OpenAI API Key, can be modified to scan an internal network in the target lobe-web environment. This issue has been addressed in release version 1.19.13 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-32965 since 04/22/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.19.13 eliminates this vulnerability. Applying the patch e960a23b0c69a5762eb27d776d33dac443058faf is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Chat Software

Vendor

• lobehub

Name

• lobe-chat

Version

• 1.19.0
• 1.19.1
• 1.19.2
• 1.19.3
• 1.19.4
• 1.19.5
• 1.19.6
• 1.19.7
• 1.19.8
• 1.19.9
• 1.19.10
• 1.19.11
• 1.19.12

License

• open-source

Website

• Product: https://github.com/lobehub/lobe-chat/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion