NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-27088: S3-Proxy allows Reflected Cross-site Scripting (XSS) in template implementation

highCVSS 4.0 8.4GHSA-pp9m-qf39-hxjc

Summary A Reflected Cross-site Scripting (XSS) vulnerability enables attackers to create malicious URLs that, when visited, inject scripts into the web application. This can lead to session hijacking or phishing attacks on a trusted domain, posing a high risk to all users. Details Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer.

Published Feb 20, 2025 · Updated Feb 21, 2025

Affected packages

github.com/oxyno-zeta/s3-proxy/cmd/s3-proxy

Ecosystem
Go
Affected
<= 0.0.0-20250212215955-2873011f7c42
Fixed in
0.0.0-20250220214310-c611c741ed48
Check
go list -m github.com/oxyno-zeta/s3-proxy/cmd/s3-proxy

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

A Reflected Cross-site Scripting (XSS) vulnerability enables attackers to create malicious URLs that, when visited, inject scripts into the web application. This can lead to session hijacking or phishing attacks on a trusted domain, posing a high risk to all users.

Details

_Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer._ It's possible to inject html elements, including scripts through the folder-list template. It seems like the .Request.URL.Path variable is not escaped.

I did some research and found it might be due to the text/template import being used in the template implementation, instead of the safer html/template.

PoC

_Complete instructions, including specific configuration details, to reproduce the vulnerability._ Using the default template configuration, the vulnerability can be reproduced with the following steps.

  1. Navigate to https://your-s3-proxy.com/path-not-found and confirm the page looks as follows:

image

  1. Try inserting an HTML element by changing /path-not-found to / and confirm the page looks as follows:

image

  1. Now it should be possible to run any JavaScript by manipulating the `onerror` property of the img element. This should make the link look like https://your-s3-proxy.com/. Confirm that going to this URL will in fact shows an alert in the browser.

Impact

The affected template allows users to interact with the URL path provided by the Request.URL.Path variable, which is then rendered directly into the HTML without proper sanitization or escaping. This can be abused by attackers who craft a malicious URL containing injected HTML or JavaScript. When users visit such a URL, the malicious script will be executed in the user's context, leading to potential risks such as:

  • Session Hijacking: Malicious scripts could be used to steal session cookies or other sensitive information.
  • Phishing Attacks: JavaScript could be injected to trick users into submitting sensitive information, such as login credentials.

This vulnerability can be exploited by attackers who craft URLs containing malicious payloads, which would then execute in the user's browser when they access the affected page. This poses a high risk to all users who visit such URLs.

Credited to ddvleeuwen, oxyno-zeta.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology