Lookup for vulnerable packages by Package URL.
| Purl | pkg:pypi/indico@1.2.1rc7 |
|---|
| Type | pypi |
|---|
| Namespace | |
|---|
| Name | indico |
|---|
| Version | 1.2.1rc7 |
|---|
| Qualifiers |
|
|---|
| Subpath | |
|---|
| Is_vulnerable | true |
|---|
| Next_non_vulnerable_version | 3.3.4 |
|---|
| Latest_non_vulnerable_version | 3.3.4 |
|---|
| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-3ev2-cjep-w3fd |
| vulnerability_id |
VCID-3ev2-cjep-w3fd |
| summary |
Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. In Indico prior to version 3.3.4, corresponding to Flask-Multipass prior to version 0.5.5, there is a Cross-Site-Scripting vulnerability during account creation when redirecting to the `next` URL. Exploitation requires initiating the account creation process with a maliciously crafted link, and then finalizing the signup process. Because of this, it can only target newly created (and thus unprivileged) Indico users. Indico 3.3.4 upgrades the dependency on Flask-Multipass to version 0.5.5, which fixes the issue. Those who build the Indico package themselves and cannot upgrade can update the `flask-multipass` dependency to `>=0.5.5` which fixes the vulnerability. Otherwise one could configure one's web server to disallow requests containing a query string with a `next` parameter that starts with `javascript:`. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2024-45399, GHSA-rrqf-w74j-24ff, PYSEC-2024-90
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-3ev2-cjep-w3fd |
|
| 1 |
| url |
VCID-n2kf-a5f2-h7d2 |
| vulnerability_id |
VCID-n2kf-a5f2-h7d2 |
| summary |
Indico is an open source a general-purpose, web based event management tool. There is a Cross-Site-Scripting vulnerability in confirmation prompts commonly used when deleting content from Indico. Exploitation requires someone with at least submission privileges (such as a speaker) and then someone else to attempt to delete this content. Considering that event organizers may want to delete suspicious-looking content when spotting it, there is a non-negligible risk of such an attack to succeed. The risk of this could be further increased when combined with some some social engineering pointing the victim towards this content. Users need to update to Indico 3.2.6 as soon as possible. See the docs for instructions on how to update. Users who cannot upgrade should only let trustworthy users manage categories, create events or upload materials ("submission" privileges on a contribution/event). This should already be the case in a properly-configured setup when it comes to category/event management. Note that a conference doing a Call for Abstracts actively invites external speakers (who the organizers may not know and thus cannot fully trust) to submit content, hence the need to update to a a fixed version ASAP in particular when using such workflows. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2023-37901, GHSA-fmqq-25x9-c6hm, PYSEC-2023-129
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-n2kf-a5f2-h7d2 |
|
| 2 |
|
|
|---|
| Fixing_vulnerabilities |
|
|---|
| Risk_score | null |
|---|
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:pypi/indico@1.2.1rc7 |
|---|