NetSight
medium5.7

CVE-2025-46551

JRuby-OpenSSL has hostname verification disabled by default

Impact

### Summary When verifying SSL certificates, jruby-openssl is not verifying that the hostname presented in the certificate matches the one we are trying to connect to, meaning a MITM could just present _any_ valid cert for a completely different domain they own, and JRuby wouldn't complain. ### Details n/a ### PoC An example domain bad.substitutealert.com was created to present the a certificate for the domain s8a.me. The following script run in IRB in CRuby 3.4.3 will fail with `certificate verify failed (hostname mismatch)`, but will work just fine in JRuby 10.0.0.0 and JRuby 9.4.2.0, both of which use jruby-openssl version 0.15.3 ```ruby require "net/http" require "openssl" uri = URI("https://bad.substitutealert.com/") https = Net::HTTP.new(uri.host, uri.port) https.use_ssl = true https.verify_mode = OpenSSL::SSL::VERIFY_PEER body = https.start { https.get(uri.request_uri).body } puts body ``` ### Impact Anybody using JRuby to make requests of external APIs, or scraping the web, that depends on https to connect securely

Affected packages

EcosystemPackageAffectedFixed in
mavenrubygems:jruby-openssl>= 0.12.1, < 0.15.40.15.4
mavenorg.jruby:jruby>= 10.0.0.0, < 10.0.0.110.0.0.1
rubygemsjruby-openssl>= 0.12.1, < 0.15.40.15.4

Affected products

VendorProductAffected versions
JrubyJruby
from 9.3.4.0 before 9.4.12.1
Version 10.0.0.0
JrubyJruby-Openssl
from 0.12.1 before 0.15.4

Weakness classification

References