Private-key disclosure via malformed SubjectKeyId
Published Jul 1, 2025 · Updated Jul 1, 2025
Cleartext key storage in Canonical Juju Utils 4.0.1 through 4.0.3 allows attackers to extract a private key from a certificate. cert.NewLeaf passes the Ed25519 private key as the prefix argument to sha512.New384().Sum, so SubjectKeyId contains the key followed by an empty-input digest. Exposure requires a generated client or server certificate to cross the network; a server TLS handshake can disclose its key, while a client must connect to an attacker-controlled server.
Summary
What happened
Cleartext key storage in Canonical Juju Utils 4.0.1 through 4.0.3 allows attackers to extract a private key from a certificate. cert.NewLeaf passes the Ed25519 private key as the prefix argument to sha512.New384().Sum, so SubjectKeyId contains the key followed by an empty-input digest. Exposure requires a generated client or server certificate to cross the network; a server TLS handshake can disclose its key, while a client must connect to an attacker-controlled server.
The record
- CVE
- CVE-2025-6224
- Published
- Jul 1, 2025
- Updated
- Jul 1, 2025
- Vendor
- Canonical
- Product
- Juju Utils
- Classifications
- CWE-312, CAPEC-131, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2025CVE publishedPublication date reported by the CVE source.
- Jul 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.0.1 <=4.0.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Go Playground certificate key-leak proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo