ruby: Incorrect checks for validity of X.509 certificates
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 4 | |||
| ruby-0:1.8.1-7.el4_8.3 | cpe:/o:redhat:enterprise_linux:4 | RHSA-2009:1140 | 2009-07-02T00:00:00Z |
| Red Hat Enterprise Linux 5 | |||
| ruby-0:1.8.5-5.el5_3.7 | cpe:/o:redhat:enterprise_linux:5 | RHSA-2009:1140 | 2009-07-02T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-1860-1 | New Ruby packages fix several issues |
EUVD |
EUVD-2009-0645 | 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. |
Ubuntu USN |
USN-805-1 | Ruby vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.6% (2.640% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.