Summary
A missing authorization check in Incus allows restricted project users to supply configuration overrides when migrating instances between cluster members. By changing security-sensitive settings, an attacker may obtain a privileged container and potentially escape to the host.
Affected context
The issue occurs in Incus environments that:
- Use clustered instance migration
- Allow users in restricted projects to initiate or influence migrations
- Apply user-supplied configuration overrides during migration
- Do not enforce project restrictions on security-sensitive keys
Risk is greatest when overrides can affect settings such as security.privileged or raw.lxc, and when the resulting container has access to host-relevant capabilities or resources.
Exploit preconditions
- Attack surface: Incus cluster instance migration
- Required access: A user account with sufficient permissions to initiate or participate in an instance migration from a restricted project
- Trigger point: Processing user-supplied configuration overrides during migration to another cluster member
- Why exploitation is possible: Project restrictions are not enforced consistently for security-critical configuration keys, allowing a restricted user to request a more privileged container configuration
Why this happens
The underlying flaw is an authorization failure in the migration configuration path. Incus accepts user-controlled overrides for security-sensitive settings without applying the project-level restrictions that should govern those settings.
This behavior maps to CWE-862: Missing Authorization, because the application performs a privileged configuration operation without verifying that the requesting project or user is authorized to make that change.
Potential impact
- A restricted project user may escalate a container to privileged status
- An attacker could gain broader access to host devices or resources
- The container boundary may be weakened or escaped
- The host system could be compromised
- Other cluster workloads or data may be exposed
- Containerized workloads could be disrupted or modified
General mitigation guidance
Mitigation generally focuses on enforcing authorization and project restrictions consistently across all instance configuration paths, including migration overrides.
Common defensive patterns include:
- Apply centralized authorization checks to every security-sensitive configuration key
- Use deny-by-default handling for privileged or raw runtime options
- Permit only explicitly approved override fields during migration
- Validate requested settings against the source project and destination project policies
- Run containers with least privilege and minimize host device, capability, and filesystem exposure
- Restrict which users and services can initiate cluster migrations
- Treat migration metadata and overrides as untrusted input
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis of migration and configuration-handling code for authorization checks that occur after settings are applied
- Code review signals involving privileged configuration keys, raw runtime options, or project-bound policy decisions
- Tests that attempt restricted operations through every supported configuration and migration path
- Audit-log monitoring for restricted users changing security-sensitive settings or initiating unexpected migrations
- Policy enforcement that blocks privileged container options unless explicitly approved for the project
Automated security review tools may help identify missing authorization checks, but they should be supplemented with authorization-focused integration tests.

