Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a critical vulnerability in Incus, a system for managing containers and virtual machines. The issue allows unauthorized clients to bypass security controls, potentially enabling them to create and access resources, or even execute code with root privileges on the host system. Understanding the scope of Incus deployment within the organization is key to assessing potential impact.
- Bypassed security controls can lead to unauthorized resource access.
- It could allow code execution on host systems.
- Confirming Incus usage and exposure is the primary concern.
Attack Path
How an attacker could exploit the issue
An attacker can bypass authorization controls to create or access default project resources within Incus. By setting up bridge networks with raw.dnsmasq directives, attackers can gain root code execution on the host system. They can also manipulate inherited resources using the `?project=` parameter to compromise system integrity.
- Requires limited client access.
- Triggers with specific network directives or project parameters.
- Leads to host root code execution.
Live Threat
Current exploitation, exposure, and threat context
A restricted client could bypass authorization checks to create and access default project resources. This could lead to the execution of arbitrary code as root on the host system or manipulation of inherited resources.
- Host system or project resources.
- Bypass authorization checks.
- Root code execution or resource manipulation.
Operational Fix
Recommended remediation, mitigation, and detection steps
This critical authorization bypass vulnerability in Incus affects its entitlement checks, potentially allowing restricted clients to create and access default project resources, execute code as root on the host, or manipulate inherited resources. Real-world response typically falls to platform or infrastructure teams responsible for managing the Incus environment, in coordination with security operations for exposure assessment and application owners if Incus is used to manage application deployments. The immediate first step is to identify all Incus deployments, assess their reachability and business criticality, and then plan remediation or mitigation based on risk.
- Platform or infrastructure teams should own the issue.
- Verify Incus reachability and business criticality.
- Plan remediation based on assessed risk.