Summary
Local file disclosure through LaTeX injection
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:
- Open a thread in our forum
- Email us privately at [email protected]
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.
Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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.
Frequently Asked Questions
- What is GHSA-67CX-RHHQ-MFHQ? GHSA-67CX-RHHQ-MFHQ is a high-severity command injection vulnerability in indico (pip), affecting versions < 2.1.10. It is fixed in 2.1.10, 2.2.3. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
- Which versions of indico are affected by GHSA-67CX-RHHQ-MFHQ? indico (pip) versions < 2.1.10 is affected.
- Is there a fix for GHSA-67CX-RHHQ-MFHQ? Yes. GHSA-67CX-RHHQ-MFHQ is fixed in 2.1.10, 2.2.3. Upgrade to this version or later.
- Is GHSA-67CX-RHHQ-MFHQ exploitable, and should I be worried? Whether GHSA-67CX-RHHQ-MFHQ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-67CX-RHHQ-MFHQ is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-67CX-RHHQ-MFHQ?
- Upgrade
indicoto 2.1.10 or later - Upgrade
indicoto 2.2.3 or later
- Upgrade