Loading vulnerability…
Lobe Chat prior to version 1.19.13 is vulnerable to server-side request forgery (SSRF) due to insufficient validation of redirects in the SSRF protection logic in src/app/api/proxy/route.ts. An attacker can supply a malicious external URL that redirects to internal resources, such as private network or loopback addresses, thereby bypassing the intended SSRF protections.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2024-47066, a server-side request forgery (SSRF) vulnerability in Lobe Chat (prior to version 1.19.13). The main exploit script, CVE-2024-47066.py, is a Python program that automates the exploitation process. It works by first generating a shortened URL (using shorturl.at) that points to an internal resource. This bypasses the SSRF protection in Lobe Chat's /api/proxy endpoint, which only checks the resolved IP of the initial URL and not any redirects. The script then sends a POST request to the vulnerable endpoint with the shortened URL, causing the server to follow the redirect and access the internal resource. The repository also includes a Docker environment to simulate a vulnerable Lobe Chat instance and an internal Flask-based web service (on port 4000) for testing. The exploit demonstrates how an attacker could use this vulnerability to access internal services or sensitive cloud metadata endpoints (e.g., http://169.254.169.254). The code is well-structured, with clear separation between the exploit logic and the environment setup. The README provides detailed usage instructions and analysis of the vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.