TMA-LXD-HTTPS-ADDRESS

Ensure the LXD remote API is not listening on all interfaces

AltaNível 1Automatizadalxd

Descrição

core.https_address exposes the LXD REST API (full control of every instance and the host) over the network. The audit reads it with "lxc config get core.https_address" and passes when it is unset (local unix socket only) or bound to a specific address; it fails on wildcard binds such as [::], 0.0.0.0 or a bare :8443. The lxc client must reach the daemon (run as root or a member of the lxd group).

Como é verificado

Método de auditoria: Comando shell

shell

lxc info >/dev/null 2>&1 || exit 1
v=$(lxc config get core.https_address 2>/dev/null) || exit 1
case "$v" in
  "[::]"*|0.0.0.0*|:*) echo "remote API listens on all interfaces: $v"; exit 1 ;;
esac
echo compliant

Saída esperada: compliant

Como é corrigido

Método de correção: Orientação ou patch de infraestrutura

If remote access is not needed: lxc config unset core.https_address. Otherwise bind to the management interface only, e.g. lxc config set core.https_address 10.0.0.5:8443, and restrict port 8443 with the host firewall.

Propriedades

Sistemas operacionais: Qualquer
Tags: lxdcontainersnetwork
Referência: CIS-style LXD hardening guidance - Restrict remote API exposure (no CIS benchmark section; verify against your hardening standard)

Verificar este host

Execute isto em uma máquina que você tenha permissão para auditar. A varredura é somente leitura.

shell

tmaegis scan --target lxd