Is CVE-2024-32965 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2024-32965 being exploited in the wild.

How severe is CVE-2024-32965?

Low severity, with a CVSS score of 3.1, published 26 November 2024.

Which products and versions are affected?

@lobehub/chat (npm) SEMVER:introduced=0,fixed=1.19.13.

Is there a fix for CVE-2024-32965?

Yes. @lobehub/chat (npm): upgrade to 1.19.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2024-32965 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2024-32965?

Check whether you run LobeHub Lobe Chat or @lobehub/chat (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2024-32965: LobeHub Lobe Chat SSRF in OpenAI proxy configuration

CVE-2024-32965 · Severity: low · CVSS 3.1 · Published 2024-11-26

Lobe Chat is an open-source framework for building AI-powered chat interfaces. A security flaw allows unauthenticated attackers to trick the server into making unauthorized requests to internal network services. This could lead to the exposure of sensitive internal data or allow attackers to probe private infrastructure that is not normally accessible from the internet.

Technologies: LobeHub Lobe Chat, @lobehub/chat (npm). Vendors: LobeHub, npm.

Quick answers

Is CVE-2024-32965 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2024-32965 being exploited in the wild.
How severe is CVE-2024-32965?: Low severity, with a CVSS score of 3.1, published 26 November 2024.
Which products and versions are affected?: @lobehub/chat (npm) SEMVER:introduced=0,fixed=1.19.13.
Is there a fix for CVE-2024-32965?: Yes. @lobehub/chat (npm): upgrade to 1.19.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2024-32965 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2024-32965?: Check whether you run LobeHub Lobe Chat or @lobehub/chat (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@lobehub/chat (npm): upgrade to 1.19.13 or later
```
npm install @lobehub/chat@1.19.13
```

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Lobe Chat due to insufficient validation of the proxy address provided in the 'X-Lobe-Chat-Auth' header. An unauthenticated attacker can provide a malicious proxy endpoint (e.g., using a loopback address or internal IP) which the server will then attempt to contact to fulfill chat requests. By manipulating the JWT token in the header, an attacker can bypass intended restrictions to scan internal networks or leak sensitive information from intranet services. The vulnerability is addressed in version 1.19.13 by implementing improved SSRF protections.

Affected products

LobeHub lobe-chat < 1.19.13

Identifiers

CVE-2024-32965
GHSA-2xcc-vm3f-m8rw

Timeline

2024-11-26: advisory: GitHub Security Advisory published
2024-11-26: patched: Fixed in version 1.19.13

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.