GHSA-5C64-J5M6-8433
Restricted clients can create and access resources in the default project
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-5C64-J5M6-8433 divulgada · CVSS 9.9 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
Projects can share networks, profiles, images, storage volumes and
buckets from the default project by leaving the matching `features.*`
key disabled. Requests for such a resource are transparently redirected
to the default project.
When creating such a resource, the `can_create_*` entitlement was
checked against the requested project while the resource itself was
created in the default project. A restricted certificate has every
entitlement on the projects it is trusted for, so it could create
resources in a project it has no access to.
The same mismatch applied when acting on an already inherited resource:
the permission was checked only against the effective (default) project
the request resolved to, so a client could also reach such resources
through a `?project=` value it does not control.
This has been the case since restricted certificates were introduced.
Impact
A client restricted to a project with `features.networks` disabled,
which is the default for new projects, can create networks, network
ACLs and address sets in the default project. Bridge networks accept
the `raw.dnsmasq` key, which disables the AppArmor confinement of
dnsmasq and allows arbitrary dnsmasq directives. As dnsmasq is started
as root, this can lead to code execution as root on the host.
The same applies to network zones when `features.networks.zones` is
disabled, and to profiles, images, image aliases, custom storage
volumes and storage buckets when the matching feature is disabled on
the project.
Beyond creation, the same gap let a restricted client read, update,
rename or delete inherited resources, and read another project's
network DHCP leases, by selecting them through the `?project=`
parameter without holding access to that project.
Workarounds
Setting `restricted.networks.access` on restricted projects to the list
of existing networks they may use prevents the creation of networks.
There is no workaround for the other resource types other than
enabling the matching `features.*` key on projects used by restricted
clients, which for most keys requires the project to be empty.
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-5c64-j5m6-8433Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
