Indico has Server-Side Request Forgery (SSRF) in multiple places

Overview

Impact

Indico makes outgoing requests to user-provides URLs in various places. This is mostly intentional and part of Indico's functionality, but of course it is never intended to let you access "special" targets such as localhost or cloud metadata endpoints.

Patches

You should to update to Indico 3.3.10 as soon as possible. See the docs for instructions on how to update.

Workarounds

If you do not have IPs that expose sensitive data without authentication (typically because you do not host Indico on AWS), this vulnerability doesn't impact you and you can ignore it (but please upgrade anyway). Also, only event organizers can access endpoints where SSRF could be used to actually see the data returned by such a request. So if you trust your event organizers, the risk is also very limited.

For additional security, both before and after patching, you could also use the common proxy-related environment variables (in particular http_proxy and https_proxy) to force outgoing requests to go through a proxy that limits requests in whatever way you deem useful/necessary. These environment variables would need to be set both on the indico-uwsgi and indico-celery services. Please note that setting up such a proxy is not something we can help you with.

For more information

If you have any questions or comments about this advisory:

• Open a thread in our forum
• Email us privately at [email protected]

Affected packages

• indico < 3.3.10

Remediation

Upgrade to a patched release:

• indico 3.3.10