Skip to content

txtdot Reflected XSS vulnerability in /proxy

Moderate
artegoser published GHSA-99hj-2wwx-78m3 Mar 7, 2024

Package

txtdot/txtdot (GitHub Packages)

Affected versions

>= 1.4.0

Patched versions

None

Description

Summary

Reflected Cross-Site Scripting (XSS) vulnerability of txtdot allows remote attackers to inject arbitrary web scripts via the /proxy route.

Details

DOMPurify is used for the /get route:

const purify = DOMPurify(dom.window);
output.content = purify.sanitize(dom.document.toString());

But not for the /proxy route:

fastify.get<IProxySchema>(
'/proxy',
{ schema: ProxySchema },
async (request, reply) => {
const response = await axios.get(request.query.url);
const mime: string | undefined =
response.headers['content-type']?.toString();
const clen: string | undefined =
response.headers['content-length']?.toString();
mime && reply.header('Content-Type', mime);
clen && reply.header('Content-Length', Number(clen));
return reply.send(response.data);

So it's possible to conduct reflected XSS attacks.

PoC

  1. Visit some other sites that use non-http-only cookies, e.g. https://txt.artegoser.ru/proxy?url=https://github.com.
  2. Visit the link provided by an attacker to see your cookie: https://txt.artegoser.ru/proxy?url=https://f7rl5sws.requestrepo.com

Impact

Attackers can inject arbitrary web scripts on txtdot website by fooling a victim into visiting a malicious link.

Severity

Moderate

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
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:R/S:C/C:L/I:L/A:N

CVE ID

No known CVE

Weaknesses

Credits