CVE-2000-0549

• • cpe:2.3:a:mit:kerberos:4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:mit:kerberos:4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:mit:kerberos:4.0:patch10:*:*:*:*:*:*
• • cpe:2.3:a:mit:kerberos_5:1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:mit:kerberos_5:1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:mit:kerberos_5:1.0:patch_level1:*:*:*:*:*:*
  • cpe:2.3:a:mit:kerberos_5:1.0:patch_level2:*:*:*:*:*:*
  • cpe:2.3:a:mit:kerberos_5:1.0:patch_level3:*:*:*:*:*:*
• • cpe:2.3:a:mit:kerberos_5:1.1.1:*:*:*:*:*:*:*
• • cpe:2.3:a:mit:kerberos_5:1.1:*:*:*:*:*:*:*

This CVE has no assigned vulnerable Common Criteria or FIPS 140 certificates.