GHSA-PXJV-6QGF-XHCG
Fresh installation of TeamPass 3.2.3.1 fails at the database step (installer allowlist rejects 35 tables)
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-PXJV-6QGF-XHCG divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
TeamPass 3.2.3.1 cannot be installed from scratch. The database step of the web installer (step 5) refuses 35 of the 86 actions it is scheduled to run, each of which creates a table. The installation stops there, the configuration step is never reached and no usable instance is produced. This also applies to a first deployment of the 3.2.3.1 Docker image, which uses the same web installer.
Existing installations are not affected: upgrading to 3.2.3.1 does not go through this code, and running instances never execute it.
This is not an exploitable vulnerability: no attacker action is involved and nothing is exposed. It is published as an advisory because it blocks the deployment of the release that fixes GHSA-8xp7-fh3p-5pcr https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-8xp7-fh3p-5pcr and GHSA-988j-pf6f-2m2r https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-988j-pf6f-2m2r. An administrator who falls back to 3.2.3.0 or earlier to obtain a working installation exposes that instance to those two critical, unauthenticated remote code execution vulnerabilities.
Details
As part of the GHSA-8xp7-fh3p-5pcr fix, 3.2.3.1 replaced the installer's dynamic dispatcher (any method name sent by the client was called through `method_exists()` + `call_user_func()`) with an explicit allowlist: `installAllowedActions()` in `app/sources/install_security_logic.php`, enforced by `DatabaseInstaller::handleAction()` in `public/install/install-steps/run.step5.php`.
The step 5 list stops at `user_private_keys` (51 entries). The installer client, `public/install/install-steps/install.js`, schedules 86 actions for that step; the 35 scheduled after `user_private_keys` are not in the list:
`users_groups`, `users_groups_forbidden`, `users_roles`, `users_favorites`, `users_latest_items`, `users_options_favorites`, `encryption_migration_stats`, `websocket_events`, `websocket_connections`, `websocket_tokens`, `network_acl`, `items_corruption`, `api_tokens`, `api_sessions`, `api_rate_limit`, `import_tracking`, `item_health`, `user_nudges`, `rotation_flags`, `access_reviews`, `access_review_items`, `data_classification`, `user_notifications`, `emails_templates`, `lapr_endpoints`, `lapr_accounts`, `lapr_policies`, `lapr_audit_log`, `lapr_rate_limit`, `items_revisions`, `api_idempotency`, `webauthn_credentials`, `sharekeys_webauthn`, `user_webauthn_credentials`, `secure_send_audit`.
Each of them is answered with:
{"success": false, "message": "Query error occurred: Action not recognized: <action>"}The client marks the step as failed and keeps the Next button disabled, so step 6 (settings file, secure key, cron job, installer cleanup) is never run. The step 6 allowlist is complete, and the upgrade wizard (`public/install/upgrade.php` and `upgrade_run_*.php`) does not use this dispatcher.
Proof of concept
- Deploy TeamPass 3.2.3.1 (archive or Docker image) and open the web installer against an empty database.
- Complete steps 1 to 4, then start step 5.
- The three preparation actions and the first 48 tables succeed. From `users_groups` onwards, every line shows a red cross with `Query error occurred: Action not recognized: <table>`.
- The step ends with "Errors occurred. Please fix the issues before continuing." and the installation cannot proceed.
Impact
- Fresh installations of 3.2.3.1 are impossible, whether from the archive or the Docker image.
- No confidentiality or integrity impact, no code execution, no effect on existing or upgraded instances.
- Indirect security risk: working around the failure by installing 3.2.3.0 or an earlier release exposes the new instance to GHSA-8xp7-fh3p-5pcr and GHSA-988j-pf6f-2m2r (both critical, pre-authentication RCE).
Patches
Fixed in 3.2.3.2 (commit 7b0ed44b1). The step 5 allowlist now contains every scheduled action. A new unit test (`InstallSecurityLogicTest::testEveryScheduledSchemaActionIsExplicitlyAllowed`) reads the schedule from `install.js` and fails as soon as a scheduled action is missing from the allowlist, so a table added to the installer can no longer be left out of it.
Workarounds
- Install 3.2.3.2 or later.
- Do not install 3.2.3.0 or an earlier release to work around this issue.
- If you must install 3.2.3.1, add the 35 action names listed above to the `'step5'` array of `installAllowedActions()` in `app/sources/install_security_logic.php` before running the installer.
- After a failed attempt, the database holds no user data yet: drop and recreate it (or empty it), then run the installer again with a fixed version.
Credits
Found and fixed by @guerricv while validating a fresh installation for PR #5437.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Versiones afectadas
3.2.3.1Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Packagistnilsteampassnet/teampass |
Sin parche | — | — | — |
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-pxjv-6qgf-xhcgLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
