Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a vulnerability in Incus, a system for managing containers and virtual machines. The flaw allows unauthorized remote access to cluster-level controls by bypassing authentication mechanisms. This could potentially lead to significant compromise of the underlying infrastructure and its data.
- Bypass security to gain unauthorized access.
- Critical for infrastructure and data protection.
- Confirm relevance and understand potential exposure.
Attack Path
How an attacker could exploit the issue
An attacker could bypass authentication by intercepting and manipulating TLS client connections to Incus. By appending a trusted certificate, such as the server's own certificate or that of another cluster member, to their presented TLS client chain, an attacker can impersonate a legitimate user or service. This allows them to gain unauthorized cluster-level access, circumventing standard authorization checks and potentially altering critical trust store configurations or influencing scriptlet-based authorization logic.
- Unauthenticated network access required.
- Appending certificate to TLS client chain.
- Unauthorized cluster access and control.
Live Threat
Current exploitation, exposure, and threat context
An authentication bypass vulnerability in Incus could allow remote attackers to impersonate trusted certificates, granting them cluster-level access and the ability to modify trust store entries and influence authorization decisions. This could occur when the system is configured to accept untrusted certificates, potentially exposing sensitive cluster operations.
- Cluster access and control.
- Remote attackers bypass authentication.
- Unauthorized access and modification.
Operational Fix
Recommended remediation, mitigation, and detection steps
The remote authentication bypass vulnerability in Incus impacts cluster administration. Infrastructure or platform teams are likely responsible for managing Incus, with security teams needing to oversee its exposure and access controls. The first step is to identify all Incus deployments, determine their reachability and business criticality, and then ascertain the specific ownership for each instance to plan remediation.
- Identify Incus deployment owners.
- Verify network reachability and criticality.
- Plan remediation based on exposure.