Key leakage in juju/utils certificates
Canonical Juju utils
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/juju/utils/v4/cert Go |
|
|
| github.com/juju/utils Go |
| No fix yet |
| github.com/juju/utils/v2 Go |
|
Canonical Juju utils
| Product | Affected | Fixed in |
|---|---|---|
| github.com/juju/utils/v4/cert Go |
|
|
| github.com/juju/utils Go |
| No fix yet |
| github.com/juju/utils/v2 Go |
|
| No fix yet |
| github.com/juju/utils/v3 Go |
| No fix yet |
| github.com/juju/utils/v4 Go |
|
|
Certificate generation in juju/utils using the cert.NewLeaf function could include private information. If this certificate were then transferred over the network in plaintext, an attacker listening on that network could sniff the certificate and trivially extract the private key from it.
From the CVE record · canonical
Certificates generated by juju/utils using cert.NewLeaf could include private information. If a certificate is transferred over a network in plaintext, an attacker listening on that network could extract its private key.
Check Go applications using github.com/juju/utils/v4 or github.com/juju/utils/v4/cert before 4.0.4, or any version of github.com/juju/utils, github.com/juju/utils/v2, or github.com/juju/utils/v3.