Summary
The application contains a reflected cross-site scripting via URL-parameter ?hc=...
Details
A reflected cross-site scripting (XSS) vulnerability exists in the web interface of the application that could allow an attacker to execute malicious javascript code by tricking users into accessing a malicious link.
The worst-case outcome of this is being able to move or delete existing files on the server, or upload new files, using the account of the person who clicks the malicious link.
It is recommended to change the passwords of your copyparty accounts, unless you have inspected your logs and found no trace of attacks.
Checking for exposure
if copyparty is running behind a reverse proxy, you can check the access-logs for traces of attacks, by grepping for URLs containing ?hc=
with <
somewhere in its value, for example using the following command:
- nginx:
(gzip -dc access.log*.gz; cat access.log) | sed -r 's/" [0-9]+ .*//' | grep -E '[?&](hc|pw)=.*[<>]'
PoC
http://127.0.0.1:3923/?hc="><script>alert(1);</script>
http://127.0.0.1:3923/?pw=<script>alert(1);</script>
References
Summary
The application contains a reflected cross-site scripting via URL-parameter
?hc=...
Details
A reflected cross-site scripting (XSS) vulnerability exists in the web interface of the application that could allow an attacker to execute malicious javascript code by tricking users into accessing a malicious link.
The worst-case outcome of this is being able to move or delete existing files on the server, or upload new files, using the account of the person who clicks the malicious link.
It is recommended to change the passwords of your copyparty accounts, unless you have inspected your logs and found no trace of attacks.
Checking for exposure
if copyparty is running behind a reverse proxy, you can check the access-logs for traces of attacks, by grepping for URLs containing
?hc=
with<
somewhere in its value, for example using the following command:PoC
http://127.0.0.1:3923/?hc="><script>alert(1);</script>
http://127.0.0.1:3923/?pw=<script>alert(1);</script>
References