Bug 1076211 - (CVE-2018-5710) VUL-1: CVE-2018-5710: krb5: An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. Thepre-defined function "strlen" is getting a "NULL" string as a parameter value inplugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in the Key Di
(CVE-2018-5710)
VUL-1: CVE-2018-5710: krb5: An issue was discovered in MIT Kerberos 5 (aka kr...
Status: RESOLVED FIXED
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P4 - Low : Normal
: ---
Assigned To: Security Team bot
Security Team bot
https://smash.suse.de/issue/198324/
CVSSv3:SUSE:CVE-2018-5710:5.3:(AV:N/A...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-16 14:46 UTC by Marcus Meissner
Modified: 2019-09-04 14:39 UTC (History)
7 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Meissner 2018-01-16 14:46:16 UTC
CVE-2018-5710

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. The
pre-defined function "strlen" is getting a "NULL" string as a parameter value in
plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in the Key Distribution Center
(KDC), which allows remote authenticated users to cause a denial of service
(NULL pointer dereference) via a modified kadmin client.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-5710
https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Denial%20Of%20Service%28DoS%29
Comment 2 Alexander Bergmann 2018-03-14 09:44:02 UTC
So far, there is no upstream fix available.
Comment 3 Marcus Meissner 2018-11-29 16:00:47 UTC
this seems still unfixed.
Comment 5 Samuel Cabrero 2019-07-23 13:58:44 UTC
I am reassigning to the security team as I think this was fixed as CVE-2018-5729 and CVE-2018-5730 so this one can be closed.
Comment 6 Marcus Meissner 2019-09-04 12:31:33 UTC
Closing, as this was fixed under CVE-2018-5729 and CVE-2018-5730.