Advisory

GHSA-67cx-rhhq-mfhq

Also known as: None

Summary

High severity vulnerability that affects indico

Details

Local file disclosure through LaTeX injection

Impact
An external audit of the Indico codebase has discovered a vulnerability in Indico's LaTeX sanitization code, which could have malicious users to run unsafe LaTeX commands on the server. Such commands allowed for example to read local files (e.g. indico.conf).

As far as we know it is not possible to write files or execute code using this vulnerability.

Patches
You need to update to Indico 2.2.3 as soon as possible.
We also released Indico 2.1.10 in case you cannot update to 2.2 for some reason.
See https://docs.getindico.io/en/stable/installation/upgrade/ for instructions on how to update.

Workarounds
Setting XELATEX_PATH = None in indico.conf will result in an error when building a PDF, but without being able to run xelatex, the vulnerability cannot be abused.

For more information
If you have any questions or comments about this advisory:

Severity

High Basis: The source's own band: HIGH

Dates

Published
2019-10-11 18:28 UTC
Modified
2024-12-02 05:43 UTC

Affected packages and fixes

indico

PyPI · All systems

Affected

  • introduced 0, fixed 2.1.10 (ecosystem)

Fixed versions

2.1.10

Fix

  • Fixed version 2.1.10
    pip install --upgrade indico==2.1.10

indico

PyPI · All systems

Affected

  • introduced 2.2.0, fixed 2.2.3 (ecosystem)

Fixed versions

2.2.3

Fix

  • Fixed version 2.2.3
    pip install --upgrade indico==2.2.3

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences