Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

rubygems:jruby-openssl

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.7MavenPublished

    JRuby-OpenSSL has hostname verification disabled by default

    CVE-2025-46551 · GHSA-72qj-48g4-5xgx

    Affected
    • Maven rubygems:jruby-openssl >= 0.12.1, < 0.15.4
    Fixed in
    0.15.4· Vendor fix available
    Issue
    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 Impact Anybody using JRuby to make requests of external APIs, or scraping the web, that depends on https to connect securely

    Recommended action: Upgrade to 0.15.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →