Skip to content
Fencer Intel
high 7.5

CVE-2009-4123 json

jruby-openssl gem for JRuby fails to do proper certificate validation

published 3y ago modified 4mo ago also GHSA-xgv7-pqqh-h2w9 , EUVD-2023-0588

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

The jruby-openssl gem before 0.6 for JRuby mishandles SSL certificate validation.

Patch / fix

  • rubygems jruby-openssl 0.6
  • jruby jruby-openssl 0.6

Is CVE-2009-4123 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.60% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
rubygems jruby-openssl
<0.6
0.6

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.