Improper TLS Client/Server authentication and certificate verification on Database Cluster
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Canonical | Juju | unaffected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Canonical | Juju |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-gvrj-cjch-728p | Juju has Improper TLS Client/Server authentication and certificate verification on Database Cluster |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.388% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Canonical
Canonical juju |
|
| CPEs | cpe:2.3:a:canonical:juju:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Canonical
Canonical juju |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where the internal Dqlite database cluster fails to perform proper TLS client and server authentication. Specifically, the Juju controller's database endpoint does not validate client certificates when a new node attempts to join the cluster. An unauthenticated attacker with network reachability to the Juju controller's Dqlite port can exploit this flaw to join the database cluster. Once joined, the attacker gains full read and write access to the underlying database, allowing for total data compromise. | |
| Title | Improper TLS Client/Server authentication and certificate verification on Database Cluster | |
| Weaknesses | CWE-295 CWE-306 |
|
| References |
| |
| Metrics |
cvssV3_1
|