Ensure the LXD remote API is not listening on all interfaces

ÉlevéeNiveau 1Automatiséelxd

Description

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).

Méthode de vérification

Méthode d'audit: Commande 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

Sortie attendue: compliant

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

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.

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: lxdcontainersnetwork
Référence: CIS-style LXD hardening guidance - Restrict remote API exposure (no CIS benchmark section; verify against your hardening standard)

Vérifier cet hôte

Exécutez cette commande sur une machine que vous êtes autorisé à auditer. L'analyse est en lecture seule.

shell

tmaegis scan --target lxd