llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Packagist · nilsteampassnet/teampass

GHSA-JGMV-3GR2-FJPW

Item creation writes its role restriction onto a client-supplied item id: any user who can create an item adds role restrictions to any existing item

Parche disponible
Descargar PNG JSON
CVSS 3.1
7.1
Alta
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión3.2.4.1
Exposición17 dDesde la divulgación, 4 nov 2026, 12:47 a. m.
Detección15 dDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir
Remediar en la ventana regular de mantenimiento
Estimación de Llama con el árbol SSVC de CISA a partir de vector CVSS 3.1 y la evidencia de explotación (sin evaluación oficial): sin explotación conocida, no automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Revisa tus logs de la semana con la lupa.Puede que hoy no pase nada. Puede.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
4 nov 26
19 nov 26
21 nov 26
4 nov 26
8 nov 26
12 nov 26
17 nov 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-JGMV-3GR2-FJPW divulgada · CVSS 7.1 (GitHub)
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Summary

TeamPass items can be restricted to some users (`items.restricted_to`) and/or some roles (`restriction_to_roles`). When an item was created with a role restriction, the `new_item` web handler inserted the `restriction_to_roles` rows with the item id taken from the request's `item_id` field instead of the id of the item it had just created. Any authenticated user able to create an item, in their personal folder included, could therefore attach a role restriction, including one of their own roles, to any existing item.

Details

Paths under `app/sources/`, line numbers as of 3.2.4.0.

  • `items.queries.php:150` reads the POST field `item_id` into `$inputData['itemId']`. The `new_item` case (line 205) is gated by the session key and the read-only flag only, and never reassigns that value. The item is created at line 515 (`$newID = DB::insertId()`), and every other write of the case uses `$newID`.
  • `items.queries.php:729-750`: when the `restricted_to_roles` option is enabled, each submitted role is inserted with `'item_id' => $inputData['itemId']`. Nothing ties that id to the caller or to the new item.
  • The role loop calls `count($role)`, which requires an array. The creation form posts plain role ids, so on PHP 8 the loop throws a `TypeError` after the item has been saved: a role restriction chosen at creation was never stored, and the new item stayed unrestricted by role. A crafted request whose roles are arrays passes the loop and reaches the insert.
Proof of concept

On an instance with `restricted_to_roles` enabled, user U holds role R and can create an item (a personal folder is enough). Item V, owned by someone else, is restricted to other users. As U, send the `new_item` request with `item_id=<V>` and a role list whose entry is an array naming R. The new item is created, and `restriction_to_roles` gains the row `(role_id = R, item_id = V)`.

Preconditions
  • The `restricted_to_roles` option is enabled (Settings > Options).
  • The attacker is authenticated and can create an item.
  • To read the target afterwards, the attacker must also be able to open its folder.
Impact

Adding one of their own roles to an item restricted to other users grants the attacker access to that item, current password included, when they can open its folder (shared items are keyed for every user). Adding a role to an unrestricted item hides it from every other member of its folder. The write needs no access to the target item at all.

Patches

Fixed in 3.2.4.1: item creation attaches its role restriction to the item it has just created (`$newID`), accepts the plain role ids the form sends, and skips any value that is not a positive role id.

Workarounds
  • Disable the `restricted_to_roles` option until the upgrade.
  • Review `restriction_to_roles` for rows whose role was not set by the item's owner.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:L
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
8.3/ 10Alto
Vector 8.3 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida
nilsteampassnet/teampass≥ 3.0.0.0 < 3.2.4.1
3.0.0.0
3.2.4.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Packagistnilsteampassnet/teampass
Corregida 3.2.4.1 — —
Versiones corregidas3.2.4.1
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-jgmv-3gr2-fjpw

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.