留言板

Is Liferay affected by the openSSL bug (Heartbleed)

michael merker,修改在10 年前。

Is Liferay affected by the openSSL bug (Heartbleed)

New Member 帖子: 3 加入日期: 13-4-2 最近的帖子
Hi

Just wanted to know if Liferay is affected by the openSSL bug (Heartbleed)?

If not, what kind of library is Liferay using for SSL?

Regards
Michael
thumbnail
ritresh girdhar,修改在10 年前。

RE: Is Liferay affected by the openSSL bug (Heartbleed)

Junior Member 帖子: 67 加入日期: 11-7-15 最近的帖子
Hi Michael

I am also exploring same thing , And what i come to know is that "its not related to any web-server or web applications". Its about the place whereever we
used OpenSSL tool , like for creating SSL certificate or some other openssl api we used. That can be effected .

http://mashable.com/2014/04/09/heartbleed-bug-websites-affected/
https://wiki.bitnami.com/security/2014-04_Heartbleed_Bug
http://community.bitnami.com/t/heartbleed-and-bitnami/23497 .
Sherry Bastion,修改在10 年前。

RE: Is Liferay affected by the openSSL bug (Heartbleed)

New Member 发布: 1 加入日期: 13-7-24 最近的帖子
Will someone from Liferay please issue a response?
thumbnail
James Falkner,修改在10 年前。

RE: Is Liferay affected by the openSSL bug (Heartbleed) (答复)

Liferay Legend 帖子: 1399 加入日期: 10-9-17 最近的帖子
Sherry Bastion:
Will someone from Liferay please issue a response?


Liferay itself does not contain OpenSSL, but many sites that use Liferay also use software to implement SSL that relies on OpenSSL, so depending on which version of OpenSSL you have, you might be vulnerable and need to update it (More information about how to know if you are affected and how to update is here). There's no patch for Liferay necessary though, just update OpenSSL and revoke/re-issue certs (and invalidate HTTP/HTTPS sessions, and so on, as described on the heartbleed page).

Liferay.com was also affected by this (see the Liferay security statement). The servers have all been updated, and we are in the process of revoking/re-issuing the SSL certs as an added precaution. There's no evidence of a breach (although this particular vulnerability doesn't leave a trace, so that's not saying much). Once the certs are updated (hopefully very soon, like in the next few days), you'll want to change your password (but not before that). We are going to send out more announcements once this is done instructing users of liferay.com what to do. I'll post here as well once it's done.
thumbnail
David H Nebinger,修改在10 年前。

RE: Is Liferay affected by the openSSL bug (Heartbleed) (答复)

Liferay Legend 帖子: 14915 加入日期: 06-9-2 最近的帖子
To clarify, Liferay itself is not affected, but your application container may be.

I tested my site using http://filippo.io/Heartbleed and found I was affected. Updated SSL on my gentoo box, restarted apache httpd & tomcat, and I was no longer affected.
thumbnail
Jack Bakker,修改在10 年前。

RE: Is Liferay affected by the openSSL bug (Heartbleed)

Liferay Master 帖子: 978 加入日期: 10-1-3 最近的帖子
David H Nebinger:
http://filippo.io/Heartbleed


above is good, also you can do below command on linux to check version of OpenSSL
curl --head http://my.domain.ca

on linux distro/versions where latest openssl 1.0.1g is avail for the release, then an 'apt-get upgrade openssl' then restart of apache can do the trick, there are older linux that requires from source, and then even older linux that aren't even affected...

Windows apache is pain tho as openssl lib is embedded Apache distro package... there is a Windows with OpenSSL v1.0.1g here: http://www.apachelounge.com/download/additional/ ; but takes a reinstall of Apache and then also perhaps a mod_jk update to match with Tomcat

--
of course I am referencing for those using apache in front of Tomcat
thumbnail
Jack Bakker,修改在10 年前。

RE: Is Liferay affected by the openSSL bug (Heartbleed)

Liferay Master 帖子: 978 加入日期: 10-1-3 最近的帖子
It's a real bug, but really I suspect most are not victim to any compromise ; don't know really. But now that almost everyone knows including criminals looking to take advantage on this : fix it first (and soon), revoke/reissue certs, change passwords, and monitor for breach (as anyone should do anyways on an ongoing basis).