Quick answers
- Is CVE-2024-32964 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-32964 being exploited in the wild.
- How severe is CVE-2024-32964?
- Low severity, with a CVSS score of 3.1, published 10 May 2024.
- Which products and versions are affected?
- @lobehub/chat (npm) SEMVER:introduced=0,fixed=0.150.6.
- Is there a fix for CVE-2024-32964?
- Yes. @lobehub/chat (npm): upgrade to 0.150.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-32964 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2024-32964?
- Check whether you run @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 0.150.6 or later
npm install @lobehub/chat@0.150.6
Technical details
The vulnerability is a Server-Side Request Forgery (SSRF) in the /api/proxy endpoint that fails to properly validate or restrict the target URLs. An unauthenticated attacker can craft POST requests to /api/proxy with arbitrary internal IP addresses or hostnames, causing the server to make requests on their behalf and return the response. The vulnerability exists in versions <= 0.150.5 and was fixed in version 0.150.6. No authentication is required; the attack vector is network-based with low attack complexity. An attacker can access internal services (CWE-918), exfiltrate sensitive data, and potentially pivot to internal infrastructure.
Affected products
- lobe-chat lobe-chat <= 0.150.5
Identifiers
- CVE-2024-32964
- GHSA-mxhq-xw3g-rphc
Timeline
- 2024-05-10: disclosed
- 2024-05-10: patched: Version 0.150.6 released with fix