Skip to content

txtdot SSRF vulnerability in /get

High
artegoser published GHSA-4gj5-xj97-j8fp Mar 7, 2024

Package

txtdot/txtdot (GitHub Packages)

Affected versions

<= 1.6.1

Patched versions

1.7.0

Description

Summary

Serveral Server-Side Request Forgery (SSRF) vulnerability in the /get route of txtdot allows remote attackers to use the server as a proxy to send HTTP GET requests to arbitrary targets and retrieve information in the internal network.

Details

The URL from user input is checked to be not local:

if (await isLocalResource(urlObj)) {
throw new LocalResourceError();
}
const response = await axios.get(remoteUrl);

export default async function isLocalResource(url: URL): Promise<boolean> {
// Resolve domain name
const addr = (await dns.promises.lookup(url.hostname)).address;
// Check if IP is in local network
return ipRangeCheck(addr, subnets);
}

But it only checks the first DNS resolution result, not subsequent HTTP redirections or later changed DNS resolution results. So it's still possible to send requests to local addresses.

PoC

302 redirect to localhost:8080: https://txt.artegoser.ru/get?url=http://6f7iwg44.requestrepo.com

DNS rebinding: https://txt.dc09.ru/get?url=http://rebinding.6f7iwg44.requestrepo.com:8080 (need to try multiple times before success)

Impact

Remote attackers can retrieve information in the internal network.

Patch

Version 1.7.0 prevents displaying the response of forged requests, but the requests can still be sent. For complete mitigation, a firewall between txtdot and other internal network resources should be set.

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVE ID

CVE-2024-41812

Weaknesses

Credits