CVE-2009-0642 json
ext/openssl/ossl_ocsp.c in Ruby 1.8 and 1.9 does not properly check the return value from the OCSP_basic_verify function, which might allow…
published 2009-02-18 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0645
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
ext/openssl/ossl_ocsp.c in Ruby 1.8 and 1.9 does not properly check the return value from the OCSP_basic_verify function, which might allow remote attackers to successfully present an invalid X.509 certificate, possibly involving a revoked certificate.
Patch / fix
- ruby RHEL 4 1.8.1-7.el4_8.3
- ruby RHEL 5 1.8.5-5.el5_3.7
- irb RHEL 4 1.8.1-7.el4_8.3
- ruby-ri RHEL 5 1.8.5-5.el5_3.7
- ruby-irb RHEL 5 1.8.5-5.el5_3.7
- ruby-libs RHEL 4 1.8.1-7.el4_8.3
- ruby-libs RHEL 5 1.8.5-5.el5_3.7
- ruby-mode RHEL 4 1.8.1-7.el4_8.3
red hat advisories RHSA-2009:1140
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2009-0642 updated cvss 5.0
ruby: Incorrect checks for validity of X.509 certificates
-
Red Hat Enterprise Linux (v. 5 server) ruby 1.8.5-5.el5_3.7, ruby-ri 1.8.5-5.el5_3.7, ruby-irb 1.8.5-5.el5_3.7, ruby-libs 1.8.5-5.el5_3.7, ruby-mode 1.8.5-5.el5_3.7, ruby-rdoc 1.8.5-5.el5_3.7, +1 more Red Hat Enterprise Linux AS version 4 irb 1.8.1-7.el4_8.3, ruby 1.8.1-7.el4_8.3, ruby-libs 1.8.1-7.el4_8.3, ruby-mode 1.8.1-7.el4_8.3, ruby-tcltk 1.8.1-7.el4_8.3 Red Hat Enterprise Linux Desktop (v. 5 client) ruby 1.8.5-5.el5_3.7, ruby-ri 1.8.5-5.el5_3.7, ruby-irb 1.8.5-5.el5_3.7, ruby-libs 1.8.5-5.el5_3.7, ruby-mode 1.8.5-5.el5_3.7, ruby-rdoc 1.8.5-5.el5_3.7, +1 more Red Hat Enterprise Linux Desktop version 4 irb 1.8.1-7.el4_8.3, ruby 1.8.1-7.el4_8.3, ruby-libs 1.8.1-7.el4_8.3, ruby-mode 1.8.1-7.el4_8.3, ruby-tcltk 1.8.1-7.el4_8.3 Red Hat Enterprise Linux Desktop Workstation (v. 5 client) ruby 1.8.5-5.el5_3.7, ruby-ri 1.8.5-5.el5_3.7, ruby-irb 1.8.5-5.el5_3.7, ruby-libs 1.8.5-5.el5_3.7, ruby-mode 1.8.5-5.el5_3.7, ruby-rdoc 1.8.5-5.el5_3.7, +1 more Red Hat Enterprise Linux ES version 4 irb 1.8.1-7.el4_8.3, ruby 1.8.1-7.el4_8.3, ruby-libs 1.8.1-7.el4_8.3, ruby-mode 1.8.1-7.el4_8.3, ruby-tcltk 1.8.1-7.el4_8.3fixed: vendor fix RHSA-2009:1140
+1 more productsfewer
Red Hat Enterprise Linux WS version 4 irb 1.8.1-7.el4_8.3, ruby 1.8.1-7.el4_8.3, ruby-libs 1.8.1-7.el4_8.3, ruby-mode 1.8.1-7.el4_8.3, ruby-tcltk 1.8.1-7.el4_8.3
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.64% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- redmine.ruby-lang.org http://redmine.ruby-lang.org/issues/show/1091 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
redmine.ruby-lang.org
/issues/show/1091
exploit
-
redhat.com
/support/errata/RHSA-2009-1140.html
vendor-advisory
-
ubuntu.com
/usn/USN-805-1
vendor-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2009:193
vendor-advisory
-
secunia.com
/advisories/35937
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/48761
vdb-entry
-
securityfocus.com
/bid/33769
vdb-entry
-
securitytracker.com
/id?1022505
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11450
vdb-entry, signature
-
secunia.com
/advisories/35699
third-party-advisory
- bugs.debian.org /cgi-bin/bugreport.cgi?bug=513528
-
secunia.com
/advisories/33750
third-party-advisory
Sources
- CVE List CVE-2009-0642
- NVD CVE-2009-0642
Fencer Vulns 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.