Descrizione
Flowintel contains a privilege escalation vulnerability in its Matrix relay (bot) integration. When the relay forwarded API requests on behalf of a represented user, the authorization and permission checks evaluated the relay bot's elevated role while the request handlers acted as the lower-privileged represented user. This mismatch allowed users with restricted roles (e.g., Read Only) to perform write operations, directory lookups, calendar modifications, assignment changes, template creation, and import actions they were not authorized to perform. Additionally, relay authority was determined by matching editable user profile fields (name and email) rather than a protected, non-spoofable identifier. An ordinary user who modified their profile to match the expected bot name could be recognized as the trusted relay, enabling impersonation of the bot and potential access to its elevated privileges. Preconditions: - A valid Flowintel user account with a restricted role (e.g., Read Only) - Access to the Matrix relay integration or the ability to send API requests with the relay's API key and a MATRIX-ID header - For the impersonation vector: ability to edit one's own profile name fields Security impact: - Unauthorized write operations by users with read-only or otherwise restricted permissions - Potential impersonation of the trusted relay bot by ordinary users - Bypass of organization-level access controls and role-based restrictions - Unauthorized modification of cases, tasks, calendar events, templates, and user directory entries Affected versions: Flowintel prior to 4.1.0
Come correggere
Priorità: Bassa — correggere con la manutenzione ordinaria. Motivazione: CVSS 6.3.
Versioni da aggiornare
Il record non riporta ancora i prodotti e le versioni corrette (analisi NVD in corso). Consultare l'advisory del vendor nei riferimenti.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Non esporre l'interfaccia di gestione su Internet: consentire l'accesso solo da reti fidate e verificare la presenza di account, sessioni o chiavi non autorizzate.
- Restringere l'accesso al componente, applicare il principio del minimo privilegio e controllare i log per operazioni non autorizzate.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.