cvelistv5 - cve-2023-37901

URL	Tags
security-advisories@github.com	https://docs.getindico.io/en/stable/installation/upgrade/	Product
security-advisories@github.com	https://github.com/indico/indico/commit/2ee636d318653fb1ab193803dafbfe3e371d4130	Patch
security-advisories@github.com	https://github.com/indico/indico/releases/tag/v3.2.6	Release Notes
security-advisories@github.com	https://github.com/indico/indico/security/advisories/GHSA-fmqq-25x9-c6hm	Vendor Advisory

▼	Vendor	Product
	indico	indico

ghsa-fmqq-25x9-c6hm

Vulnerability from github

Published

2023-07-21 20:24

Modified

2024-09-23 17:02

Severity ?

5.4 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
5.3 (Medium) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Summary

Indico vulnerable to Cross-Site-Scripting via confirmation prompts

Details

Impact

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.

Patches

You need to update to Indico 3.2.6 as soon as possible. See the docs for instructions on how to update.

Workarounds

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.

For more information

If you have any questions or comments about this advisory:

Open a thread in our forum
Email us privately at indico-team@cern.ch

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "indico"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.2.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-37901"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-07-21T20:24:10Z",
    "nvd_published_at": "2023-07-21T19:15:10Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nThere is a Cross-Site-Scripting vulnerability in confirmation prompts commonly used when deleting content from Indico.\nExploitation requires someone with at least submission privileges (such as a speaker) and then someone else to attempt to delete this content.\n\nConsidering 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.\n\n### Patches\nYou need to update to [Indico 3.2.6](https://github.com/indico/indico/releases/tag/v3.2.6) as soon as possible.\nSee [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update.\n\n### Workarounds\nOnly 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.\n\nNote 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.\n\nFor more information\n\nIf you have any questions or comments about this advisory:\n\n* Open a thread in [our forum](https://talk.getindico.io/)\n* Email us privately at [indico-team@cern.ch](mailto:indico-team@cern.ch)",
  "id": "GHSA-fmqq-25x9-c6hm",
  "modified": "2024-09-23T17:02:05Z",
  "published": "2023-07-21T20:24:10Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/indico/indico/security/advisories/GHSA-fmqq-25x9-c6hm"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-37901"
    },
    {
      "type": "WEB",
      "url": "https://github.com/indico/indico/commit/2ee636d318653fb1ab193803dafbfe3e371d4130"
    },
    {
      "type": "WEB",
      "url": "https://docs.getindico.io/en/stable/installation/upgrade"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/indico/indico"
    },
    {
      "type": "WEB",
      "url": "https://github.com/indico/indico/releases/tag/v3.2.6"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pypa/advisory-database/tree/main/vulns/indico/PYSEC-2023-129.yaml"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Indico vulnerable to Cross-Site-Scripting via confirmation prompts"
}

pysec-2023-129

Vulnerability from pysec

Published

2023-07-21 19:15

Modified

2023-07-31 20:36

Severity ?

5.4 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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.

Aliases

JSON

To clipboard

{
  "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"
    }
  ]
}

gsd-2023-37901

Vulnerability from gsd

Modified

2023-12-13 01:20

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.

Aliases

CVE-2023-37901

Aliases

CVE-2023-37901

JSON

To clipboard

{
  "GSD": {
    "alias": "CVE-2023-37901",
    "id": "GSD-2023-37901"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2023-37901"
      ],
      "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": "GSD-2023-37901",
      "modified": "2023-12-13T01:20:24.807237Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "security-advisories@github.com",
        "ID": "CVE-2023-37901",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "indico",
                    "version": {
                      "version_data": [
                        {
                          "version_affected": "=",
                          "version_value": "\u003c 3.2.6"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "indico"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "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."
          }
        ]
      },
      "impact": {
        "cvss": [
          {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.4,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "CHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
            "version": "3.1"
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "cweId": "CWE-79",
                "lang": "eng",
                "value": "CWE-79: Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://github.com/indico/indico/security/advisories/GHSA-fmqq-25x9-c6hm",
            "refsource": "MISC",
            "url": "https://github.com/indico/indico/security/advisories/GHSA-fmqq-25x9-c6hm"
          },
          {
            "name": "https://github.com/indico/indico/commit/2ee636d318653fb1ab193803dafbfe3e371d4130",
            "refsource": "MISC",
            "url": "https://github.com/indico/indico/commit/2ee636d318653fb1ab193803dafbfe3e371d4130"
          },
          {
            "name": "https://docs.getindico.io/en/stable/installation/upgrade/",
            "refsource": "MISC",
            "url": "https://docs.getindico.io/en/stable/installation/upgrade/"
          },
          {
            "name": "https://github.com/indico/indico/releases/tag/v3.2.6",
            "refsource": "MISC",
            "url": "https://github.com/indico/indico/releases/tag/v3.2.6"
          }
        ]
      },
      "source": {
        "advisory": "GHSA-fmqq-25x9-c6hm",
        "discovery": "UNKNOWN"
      }
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003c3.2.6",
          "affected_versions": "All versions before 3.2.6",
          "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
          "cwe_ids": [
            "CWE-1035",
            "CWE-79",
            "CWE-937"
          ],
          "date": "2023-07-31",
          "description": "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.",
          "fixed_versions": [
            "3.2.6"
          ],
          "identifier": "CVE-2023-37901",
          "identifiers": [
            "CVE-2023-37901",
            "GHSA-fmqq-25x9-c6hm"
          ],
          "not_impacted": "All versions starting from 3.2.6",
          "package_slug": "pypi/indico",
          "pubdate": "2023-07-21",
          "solution": "Upgrade to version 3.2.6 or above.",
          "title": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)",
          "urls": [
            "https://nvd.nist.gov/vuln/detail/CVE-2023-37901",
            "https://github.com/indico/indico/security/advisories/GHSA-fmqq-25x9-c6hm",
            "https://github.com/indico/indico/commit/2ee636d318653fb1ab193803dafbfe3e371d4130",
            "https://github.com/indico/indico/releases/tag/v3.2.6",
            "https://docs.getindico.io/en/stable/installation/upgrade/"
          ],
          "uuid": "9396af8b-51a1-47b5-8831-21628c0ad494"
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:cern:indico:*:*:*:*:*:*:*:*",
                "cpe_name": [],
                "versionEndExcluding": "3.2.6",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "security-advisories@github.com",
          "ID": "CVE-2023-37901"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "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."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-79"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/indico/indico/security/advisories/GHSA-fmqq-25x9-c6hm",
              "refsource": "MISC",
              "tags": [
                "Vendor Advisory"
              ],
              "url": "https://github.com/indico/indico/security/advisories/GHSA-fmqq-25x9-c6hm"
            },
            {
              "name": "https://github.com/indico/indico/commit/2ee636d318653fb1ab193803dafbfe3e371d4130",
              "refsource": "MISC",
              "tags": [
                "Patch"
              ],
              "url": "https://github.com/indico/indico/commit/2ee636d318653fb1ab193803dafbfe3e371d4130"
            },
            {
              "name": "https://github.com/indico/indico/releases/tag/v3.2.6",
              "refsource": "MISC",
              "tags": [
                "Release Notes"
              ],
              "url": "https://github.com/indico/indico/releases/tag/v3.2.6"
            },
            {
              "name": "https://docs.getindico.io/en/stable/installation/upgrade/",
              "refsource": "MISC",
              "tags": [
                "Product"
              ],
              "url": "https://docs.getindico.io/en/stable/installation/upgrade/"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV3": {
          "cvssV3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.4,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "CHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
            "version": "3.1"
          },
          "exploitabilityScore": 2.3,
          "impactScore": 2.7
        }
      },
      "lastModifiedDate": "2023-07-31T18:30Z",
      "publishedDate": "2023-07-21T19:15Z"
    }
  }
}

cve-2023-37901

Vulnerability from cvelistv5

Tags

Sightings

Nomenclature

Action not permitted

cve-2023-37901

Vulnerability from cvelistv5

ghsa-fmqq-25x9-c6hm

Vulnerability from github

Impact

Patches

Workarounds

pysec-2023-129

Vulnerability from pysec

gsd-2023-37901

Vulnerability from gsd

Tags

Sightings

Nomenclature