Certificate validation bypass via DNS-derived peer identity
Published May 3, 2024 · Updated Jun 17, 2025
Certificate validation in Bouncy Castle BCJSSE before 1.0.19 allows remote attackers to redirect HTTPS traffic via DNS poisoning. When HttpsURLConnection creates an SSL socket without an explicit hostname, BCJSSE derives the peer identity from the DNS-resolved address and verifies the certificate against that identity rather than the original URL hostname. Endpoint identification must be enabled, and successful DNS poisoning can cause the client to accept an attacker-controlled endpoint for the poisoned destination.
Summary
What happened
Certificate validation in Bouncy Castle BCJSSE before 1.0.19 allows remote attackers to redirect HTTPS traffic via DNS poisoning. When HttpsURLConnection creates an SSL socket without an explicit hostname, BCJSSE derives the peer identity from the DNS-resolved address and verifies the certificate against that identity rather than the original URL hostname. Endpoint identification must be enabled, and successful DNS poisoning can cause the client to accept an attacker-controlled endpoint for the poisoned destination.
The record
- CVE
- CVE-2024-34447
- Published
- May 3, 2024
- Updated
- Jun 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-297, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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