Untrusted TLS acceptance via retained GLOBALTRUST root
Published Jul 5, 2024 · Updated Feb 14, 2025
Insufficient authenticity verification in Certifi allows remote attackers to have GLOBALTRUST-rooted TLS certificate chains accepted. The bundled cacert.pem retained the self-signed GLOBALTRUST 2020 root, so TLS clients using that bundle continued to terminate trust chains at it. Exploitation requires an application to use Certifi's bundle and encounter an attacker-presented chain rooted in that certificate.
Summary
What happened
Insufficient authenticity verification in Certifi allows remote attackers to have GLOBALTRUST-rooted TLS certificate chains accepted. The bundled cacert.pem retained the self-signed GLOBALTRUST 2020 root, so TLS clients using that bundle continued to terminate trust chains at it. Exploitation requires an application to use Certifi's bundle and encounter an attacker-presented chain rooted in that certificate.
The record
- CVE
- CVE-2024-39689
- Published
- Jul 5, 2024
- Updated
- Feb 14, 2025
- Vendor
- Certifi
- Product
- certifi
- Classifications
- CWE-345, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 5, 2024CVE publishedPublication date reported by the CVE source.
- Feb 14, 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=>= 2021.5.30, < 2024.7.4
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
No public exploit references are available in this record.
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