GHSA-PF5W-M8M6-5265
Recursive and all-projects responses disclose other projects' bucket S3 keys and profile configuration to restricted clients (incomplete fix of GHSA-x8gj-2q73-qr6j)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-PF5W-M8M6-5265 divulgada · CVSS 6.5 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
A restricted TLS client that can only *view* a storage bucket can read that
bucket's S3 access key and secret key through the recursive bucket responses.
The explicit key endpoints (`GET .../buckets/{bucket}/keys` and
`GET .../buckets/{bucket}/keys/{key}`) were restricted to `can_edit` by the fix
for GHSA-x8gj-2q73-qr6j. However, the bucket detail response with recursion and
the bucket list response with `recursion=2` both embed the full key list,
including `secret-key`, and did not apply that `can_edit` check. A client with
only `can_view` on the bucket therefore obtained the credentials that the
explicit routes deny.
This is reachable in ordinary multi-tenancy: a certificate restricted to a
project with `features.storage.buckets=false` inherits the `default` project's
buckets, can view them, and so can read their S3 keys. The disclosed keys are
credentials for the bucket's object storage.
The same class of mistake affects the list endpoints that accept
`all-projects=true`: the per-object access check was evaluated against the
project named in the request rather than each object's own project. The TLS
authorizer skips its project refusal for all-projects requests and relies on
that per-object check, so it approved every object regardless of the project it
belongs to. Two listings are affected:
- `GET /1.0/storage-pools/{pool}/buckets?all-projects=true` returns the
- `GET /1.0/profiles?all-projects=true` returns the profiles of every project,
A restricted client — including one scoped to a project with no relationship to
the target, or one with an empty project list — can therefore read this data
across all projects. The profile listing needs no particular configuration and
no knowledge of resource names. Nothing is written.
Workarounds
Do not grant view access on storage buckets (or on projects that inherit the
default project's buckets) to clients that should not hold those buckets' S3
credentials; in particular review restricted certificates scoped to projects
with `features.storage.buckets=false`. S3 keys for buckets that may have been
exposed to such clients should be rotated. There is no effective workaround for
the profile listing other than upgrading.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Gogithub.com/lxc/incus/v7/cmd/incusd |
Corregida | v7.6.0 | — | — |
v7.6.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/lxc/incus/security/advisories/GHSA-pf5w-m8m6-5265Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
