Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Message-Id: <3F51893C-E378-481B-8CB4-2AFA86015262@surevine.com>
Date: Thu, 23 Apr 2015 13:05:46 +0100
From: Simon Waters <simon.waters@...evine.com>
To: oss-security@...ts.openwall.com
Subject: Incorrect handling of self signed certificates in OpenFire XMPP Server

Incorrect handling of self signed certificates in OpenFire XMPP Server


Affected software: OpenFire XMPP server
Affected versions: 3.9.3 and earlier
Vulnerabilities addressed: CVE-2014-3451, CVE-2015-2080

Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache License. It uses the widely adopted open protocol for instant messaging, XMPP (also called Jabber). 


Vulnerability details

The OpenFire server would incorrectly accept self signed certificates potentially allowing spoofing attacks.

This issue (CVE-2014-3451) is fixed in release 3.10 (OF-405). 

We would like to thank Kim Alvefur for reporting this issue.


Notes on release

The 3.10 release of OpenFire also addresses a reflected XSS issue (OF-845), and upgrades the Jetty library used (addressing CVE-2015-2080).



Release announcement (includes link to download and sha1 checksums)

https://community.igniterealtime.org/blogs/ignite/2015/04/22/openfire-3100-released <https://community.igniterealtime.org/blogs/ignite/2015/04/22/openfire-3100-released>

Simon Waters
phone  +448454681066
email  simon.waters@...evine.com <mailto:simon.waters@...evine.com>
skype  simon.waters.surevine <skype://simon.waters.surevine>

Participate | Collaborate | Innovate

Surevine Limited, registered in England and Wales with number 06726289. Mailing Address : PO Box 1136, Guildford GU1 9ND
If you think you have received this message in error, please notify us.


Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.