pysec-2023-129
Vulnerability from pysec
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.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "indico",
"purl": "pkg:pypi/indico"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2ee636d318653fb1ab193803dafbfe3e371d4130"
}
],
"repo": "https://github.com/indico/indico",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.2.6"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.98-rc1",
"0.98.0",
"0.98.1",
"0.98.2",
"0.99",
"1.0",
"1.1",
"1.1.1",
"1.1.2",
"1.2",
"1.2.1",
"1.2.1rc10",
"1.2.1rc11",
"1.2.1rc2",
"1.2.1rc4",
"1.2.1rc5",
"1.2.1rc6",
"1.2.1rc7",
"1.2.1rc9",
"1.2.2",
"1.2.2rc1",
"1.9.11.dev10",
"1.9.11.dev11",
"1.9.11.dev12",
"1.9.11.dev13",
"1.9.11.dev14",
"1.9.11.dev15",
"1.9.11.dev16",
"1.9.11.dev17",
"1.9.11.dev3",
"1.9.11.dev4",
"1.9.11.dev6",
"1.9.11.dev7",
"1.9.11.dev8",
"1.9.11.dev9",
"2.0",
"2.0.1",
"2.0.2",
"2.0.3",
"2.0a1",
"2.0rc1",
"2.0rc2",
"2.1",
"2.1.1",
"2.1.10",
"2.1.11",
"2.1.2",
"2.1.3",
"2.1.4",
"2.1.5",
"2.1.6",
"2.1.7",
"2.1.8",
"2.1.9",
"2.2",
"2.2.1",
"2.2.2",
"2.2.3",
"2.2.4",
"2.2.5",
"2.2.6",
"2.2.7",
"2.2.8",
"2.3",
"2.3.1",
"2.3.2",
"2.3.3",
"2.3.4",
"2.3.5",
"3.0",
"3.0.1",
"3.0.2",
"3.0.3",
"3.0rc1",
"3.0rc2",
"3.1",
"3.1.1",
"3.2",
"3.2.1",
"3.2.2",
"3.2.3",
"3.2.4",
"3.2.5"
]
}
],
"aliases": [
"CVE-2023-37901",
"GHSA-fmqq-25x9-c6hm"
],
"details": "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.",
"id": "PYSEC-2023-129",
"modified": "2023-07-31T20:36:08.003610+00:00",
"published": "2023-07-21T19:15:00+00:00",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/indico/indico/security/advisories/GHSA-fmqq-25x9-c6hm"
},
{
"type": "FIX",
"url": "https://github.com/indico/indico/commit/2ee636d318653fb1ab193803dafbfe3e371d4130"
},
{
"type": "WEB",
"url": "https://github.com/indico/indico/releases/tag/v3.2.6"
},
{
"type": "WEB",
"url": "https://docs.getindico.io/en/stable/installation/upgrade/"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.