CVE-2025-53640

{"id": "CVE-2025-53640", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.3, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "LOW", "vulnConfidentialityImpact": "LOW", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-07-14T21:15:27.663", "references": [{"url": "https://docs.getindico.io/en/stable/config/settings/#ALLOW_PUBLIC_USER_SEARCH", "source": "security-advisories@github.com"}, {"url": "https://docs.getindico.io/en/stable/installation/upgrade", "source": "security-advisories@github.com"}, {"url": "https://github.com/indico/indico/releases/tag/v3.3.7", "source": "security-advisories@github.com"}, {"url": "https://github.com/indico/indico/security/advisories/GHSA-q28v-664f-q6wj", "source": "security-advisories@github.com"}, {"url": "https://www.vicarius.io/vsociety/posts/cve202553640-detect-indico-vulnerability", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.vicarius.io/vsociety/posts/cve202553640-mitigate-indico-vulnerability", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-200"}, {"lang": "en", "value": "CWE-639"}, {"lang": "en", "value": "CWE-862"}]}], "descriptions": [{"lang": "en", "value": "Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. Starting in version 2.2 and prior to version 3.3.7, an endpoint used to display details of users listed in certain fields (such as ACLs) could be misused to dump basic user details (such as name, affiliation and email) in bulk. Version 3.3.7 fixes the issue. Owners of instances that allow everyone to create a user account, who wish to truly restrict access to these user details, should consider restricting user search to managers. As a workaround, it is possible to restrict access to the affected endpoints (e.g. in the webserver config), but doing so would break certain form fields which could no longer show the details of the users listed in those fields, so upgrading instead is highly recommended."}, {"lang": "es", "value": "Indico es un sistema de gesti\u00f3n de eventos que utiliza Flask-Multipass, un sistema de autenticaci\u00f3n multibackend para Flask. A partir de la versi\u00f3n 2.2 y anteriores a la 3.3.7, un endpoint utilizado para mostrar la informaci\u00f3n de los usuarios en ciertos campos (como las ACL) pod\u00eda utilizarse indebidamente para volcar informaci\u00f3n b\u00e1sica del usuario (como nombre, afiliaci\u00f3n y correo electr\u00f3nico) de forma masiva. La versi\u00f3n 3.3.7 soluciona este problema. Los propietarios de instancias que permiten a cualquier persona crear una cuenta de usuario y que deseen restringir el acceso a esta informaci\u00f3n de usuario deber\u00edan considerar restringir la b\u00fasqueda de usuarios a los administradores. Como soluci\u00f3n alternativa, es posible restringir el acceso a los endpoints afectados (por ejemplo, en la configuraci\u00f3n del servidor web); sin embargo, esto interrumpir\u00eda el funcionamiento de ciertos campos de formulario, que ya no mostrar\u00edan la informaci\u00f3n de los usuarios incluidos en ellos, por lo que se recomienda encarecidamente actualizar la versi\u00f3n."}], "lastModified": "2025-07-22T16:15:33.047", "sourceIdentifier": "security-advisories@github.com"}