/build/static/layout/Breadcrumb_cap_w.png

K1000 SSL Heartbleed bug

How quickly can we expect a patch for our K1000 and the SSL heartbleed bug?  


4 Comments   [ + ] Show comments
  • Or....is our KACE using a different version of OpenSSL that is not an issue? - statusquo 10 years ago
  • the vulnerability CVE-2014-0160 you are referring to here is only affecting "(1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g" (so 1.0.2 beta as well), this information can be retrieved via "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160";

    We are using OpenSSL 0.9.8y 5 from February 2013 on our appliances which means to our current knowledge we are not affected by this. - tk72 10 years ago
  • Here's Dell's answer:
    http://www.kace.com/support/resources/kb/solutiondetail?sol=SOL122931 - HomerM 10 years ago
  • Perfect, thank you for the replies. Just trying to make sure all my appliances and servers are updated. - statusquo 10 years ago

Answers (3)

Answer Summary:
Posted by: Nico_K 10 years ago
Red Belt
2

the K1000 and K2000 are running on a "safe" version.

the K3000 is affected.
There will be a quick patch release.
http://www.kace.com/de/support/resources/kb/solutiondetail?sol=SOL122931
(I assume this week but wwe will see)


Comments:
  • Thanks Nico_K. Just curious, which version do K1000 run on? Just good to know - johe 10 years ago
Posted by: elvenil 10 years ago
Senior Purple Belt
1

Hi guys, just to make this more clear, if I have issued the certs for the K3000 via the K1000 appliance, there's no problem? I am confused.


Comments:
  • You are still vulnerable.
    The hearbleed issue doesn't affect cert generation (or anything cryptographic at all as such), it affects how hearbeat packets sent from a client are handled internally where you can do a "buffer underflow" attack making the server leak memory contents (this is the issue..that memory content can be anything, including encryption keys, username/password, etc), you also can NOT turn this behaviour off with less than recompiling OpenSSL with the proper affected hearbeat code left out completely.

    This means that every installation of OpenSSL 1.0.1 (pre 1.0.1g) (that is connected to a network with the ability to accept encrypted connections) is very much vulnerable no matter what you do. - TomasKS 10 years ago
Posted by: tk72 10 years ago
Senior White Belt
0

the vulnerability CVE-2014-0160 you are referring to here is only affecting "(1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g" (so 1.0.2 beta as well), this information can be retrieved via "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160"; 

 

We are using OpenSSL 0.9.8y 5 from February 2013 on our appliances which means to our current knowledge we are not affected by this.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ