Information disclosure via default weak cipher suites
Published Feb 3, 2021 · Updated Aug 3, 2024
Weak cryptography in JetBrains Ktor before 1.4.2 allows remote attackers to compromise the confidentiality of TLS traffic. Ktor's default TLS configuration enabled weak cipher suites, but the vendor has not published the individual suites or the code path that selected them. Exploitation requires access to affected TLS traffic; published sources do not state whether active interception is required, and the reported impact is limited to confidentiality.
Summary
What happened
Weak cryptography in JetBrains Ktor before 1.4.2 allows remote attackers to compromise the confidentiality of TLS traffic. Ktor's default TLS configuration enabled weak cipher suites, but the vendor has not published the individual suites or the code path that selected them. Exploitation requires access to affected TLS traffic; published sources do not state whether active interception is required, and the reported impact is limited to confidentiality.
The record
- CVE
- CVE-2021-25763
- Published
- Feb 3, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 3, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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