CVE-2024-47066

[lobe-chat] Insufficient fix for GHSA-mxhq-xw3g-rphc (CVE-2024-32964)

Verified by Precogs Threat Research
Last Updated: Sep 21, 2024
Base Score
9.5CRITICAL

Executive Summary

CVE-2024-47066 is a critical severity vulnerability affecting appsec, ai-code, binary-analysis. It is classified as Server-Side Request Forgery. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"The primary vulnerability vector is rooted in within ### Summary SSRF protection, allowing an architectural oversight in input validation. An attacker can craft a specific payload to compromise the entire application stack, rendering traditional defenses ineffective. The Precogs AI's Code Property Graph analysis traces untrusted input to safeguard the application against payload injection."

Exploit Probability (EPSS)
Moderate (5.8%)
Public POC
Available
Exploit Probability
High (84%)
Public POC
Available
Affected Assets
appsecai codebinary analysisCWE-918

What is this vulnerability?

CVE-2024-47066 is categorized as a critical Application Verification Flaw flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

Summary SSRF protection implemented in https://github.com/lobehub/lobe-chat/blob/main/src/app/api/proxy/route.ts does not consider redirect and could .

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score9.5 (CRITICAL)
Vector StringN/A
PublishedSeptember 21, 2024
Last ModifiedSeptember 21, 2024
Related CWEsCWE-918

Impact on Systems

Unauthorized Access: Flaws in application logic can permit unauthorized interaction with protected APIs.

Data Manipulation: Adversaries may alter critical application states, such as user roles or configurations.

Service Disruption: Improper error handling or unvalidated inputs can lead to resource exhaustion.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Defense in Depth Implement multi-layered validation (client-side, API gateway, and server-side).

2. Least Privilege Ensure backend service accounts operate with the absolute minimum rights required.

3. Security Regression Testing Integrate automated semantic security scanning into the deployment pipeline.

Vulnerability Signature

// Generic Application Security Flaw (Node.js)
app.post('/api/update-profile', (req, res) =\> \{
    // DANGEROUS: Mass Assignment / Object Injection
    // Attacker can pass \{ "isAdmin": true, "email": "..." \}
    User.update(\{ id: req.user.id \}, req.body);
    
    // SECURED: Explicitly select permitted fields
    const \{ email, displayName, bio \} = req.body;
    User.update(\{ id: req.user.id \}, \{ email, displayName, bio \});
\});

References and Sources

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUser-supplied URL parameter
VectorServer fetches the user-controlled URL
SinkHTTP request library (e.g., fetch, axios)
ImpactAccess to internal services, metadata endpoints, or port scanning

Vulnerable Code Pattern

// ❌ VULNERABLE: Server-Side Request Forgery
app.get('/proxy', async (req, res) => {
  const targetUrl = req.query.url;
  // Taint sink: unvalidated outbound request
  const response = await fetch(targetUrl);
  res.send(await response.text());
});

Secure Code Pattern

// ✅ SECURE: Allowlist validation
const ALLOWED_DOMAINS = ['api.partner.com'];
app.get('/proxy', async (req, res) => {
  const targetUrl = new URL(req.query.url);
  
  if (!ALLOWED_DOMAINS.includes(targetUrl.hostname)) {
    return res.status(403).send("Domain not allowed");
  }
  
  // Sanitized outbound request
  const response = await fetch(targetUrl.href);
  res.send(await response.text());
});

How Precogs Detects This

Precogs API Security Engine actively detects SSRF vulnerabilities by tracking unvalidated URL sinks and enforcing strict allowlist policies.\n

Related Vulnerabilitiesvia CWE-918

CVE-2026-3543110 CRITICAL

Server-Side Request Forgery (SSRF) in Server-side request forgery (ssrf) in Microsoft Entra ID Entitlement Management allows an unauthorized attacker to perform spoofing over a network

CWE-918
CVE-2026-322109.3 CRITICAL

Server-Side Request Forgery (SSRF) in Server-side request forgery (ssrf) in Microsoft Dynamics 365 (Online) allows an unauthorized attacker to perform spoofing over a network

CWE-918
CVE-2026-3218610 CRITICAL

Server-Side Request Forgery (SSRF) in Server-side request forgery (ssrf) in Microsoft Bing allows an unauthorized attacker to elevate privileges over a network

CWE-918
CVE-2026-48740 LOW

CVE-2026-4874: Server-Side Request Forgery in Keycloak

CWE-918
CVE-2026-45287.3 HIGH

A vulnerability was determined in trueleaf ApiFlow 0.

CWE-918
CVE-2024-562796.5 MEDIUM

Server-Side Request Forgery (SSRF) — Cloud metadata access

CWE-918

Is your system affected?

Precogs AI detects CVE-2024-47066 in compiled binaries, LLMs, and application layers — even without source code access.