Juju controllers are vulnerable to total data compromise because the internal Dqlite database fails to authenticate new nodes, allowing unauthenticated attackers to gain full database access.

The Juju controller's Dqlite database endpoint fails to perform proper TLS client and server authentication. This allows an unauthenticated attacker with network access to the Dqlite port to join the cluster without a valid certificate, bypassing all security checks.

This vulnerability carries a maximum CVSS score of 10.0. An attacker joining the database cluster gains full read and write access to all Juju configuration and state data, leading to total compromise of the managed environment, including secrets and credentials.

Immediate Action: Update Juju to the latest patched versions (consult Canonical's advisory for the specific 3.x and 4.x release targets).

Proactive Monitoring: Inspect network traffic for unauthorized connections to the Juju controller's Dqlite port (typically 17017) and audit the Dqlite cluster membership for unknown nodes.

Compensating Controls: Restrict network access to the Juju controller's Dqlite port using firewalls or security groups to allow only known, trusted controller nodes.

Public Exploit Available: No

The CVSS score of 10.0 demands immediate remediation. Administrators must patch Juju controllers and strictly enforce network-level access controls to the database ports to prevent unauthorized cluster joining.