Skip to content
Fencer Intel
medium 4.3

CVE-2010-0433 json

The kssl_keytab_is_available function in ssl/kssl.c in OpenSSL before 0.9.8n, when Kerberos is enabled but Kerberos configuration files can…

published 2010-03-05 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-0464

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.9%
EPSS 7.9% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

The kssl_keytab_is_available function in ssl/kssl.c in OpenSSL before 0.9.8n, when Kerberos is enabled but Kerberos configuration files cannot be opened, does not check a certain return value, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via SSL cipher negotiation, as demonstrated by a chroot installation of Dovecot or stunnel without Kerberos configuration files inside the chroot.

Patch / fix

  • openssl RHEL 5 0.9.8e-12.el5_4.6
  • openssl-perl RHEL 5 0.9.8e-12.el5_4.6

red hat advisories RHSA-2010:0162

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-2010-0433 updated cvss 4.3

openssl: crash caused by a missing krb5_sname_to_principal() return value check

  • Red Hat Enterprise Linux (v. 5 server) openssl 0.9.8e-12.el5_4.6, openssl-perl 0.9.8e-12.el5_4.6 Red Hat Enterprise Linux Desktop (v. 5 client) openssl 0.9.8e-12.el5_4.6, openssl-perl 0.9.8e-12.el5_4.6 Red Hat Enterprise Linux Desktop Workstation (v. 5 client) openssl 0.9.8e-12.el5_4.6, openssl-perl 0.9.8e-12.el5_4.6
    fixed: vendor fix RHSA-2010:0162

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

7.86% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

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.