Bug 17474 - gajim new security issue CVE-2015-8688
Summary: gajim new security issue CVE-2015-8688
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
URL: http://lwn.net/Vulnerabilities/671445/
Whiteboard: advisory MGA5-64-OK
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2016-01-11 21:19 CET by David Walser
Modified: 2016-02-05 18:27 CET (History)
4 users (show)

See Also:
Source RPM: gajim-0.16-0.beta1.4.mga5.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2016-01-11 21:19:04 CET
A security issue in gajim was announced on December 27:
http://gultsch.de/gajim_roster_push_and_message_interception.html

It was fixed upstream in gajim 0.16.5 on December 28.

Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2016-01-12 00:33:18 CET
Updated packages uploaded for Mageia 5 and Cauldron.

Advisory:
========================

Updated gajim package fixes security vulnerability:

Gajim before 0.16.5 doesnât verify the origin of roster pushes thus allowing
third parties to modify the roster via a man-in-the-middle attack
(CVE-2015-8688).

References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8688
http://gultsch.de/gajim_roster_push_and_message_interception.html
========================

Updated packages in core/updates_testing:
========================
gajim-0.16.5-1.mga5

from gajim-0.16.5-1.mga5.src.rpm

Assignee: bugsquad => qa-bugs

Comment 2 David Walser 2016-01-14 18:43:38 CET
Fedora has issued an advisory for this today (January 14):
https://lists.fedoraproject.org/pipermail/package-announce/2016-January/175503.html
Dave Hodgins 2016-01-19 22:29:28 CET

CC: (none) => davidwhodgins
Whiteboard: (none) => advisory

Comment 3 Lewis Smith 2016-02-02 10:35:03 CET
Trying M5 x64

I wish I knew something about what Jabber is about...
Installed issued: gajim-0.16-0.beta1.4.mga5
which pulled in a few Python extras.
Found (via https://xmpp.net/directory.php) a sensible looking site
 http://jabber.apinc.org/
which helpfully suggested using the Jabber client itself to 'join up' citing serverID im.apinc.org . Which I did, it worked; then tried sending messages to myself which got bounced sort of "unable to find server".

BTAIM I updated to: gajim-0.16.5-1.mga5
after which it did not start at all. From console:
 $ gajim
 Gajim needs python-nbxmpp >= 0.5.3 to run. Quiting...
So it looks as if something needs adding to the update.

CC: (none) => lewyssmith
Whiteboard: advisory => advisory feedback

Comment 4 David Walser 2016-02-02 13:52:15 CET
Updated packages uploaded for Mageia 5 and Cauldron.

Advisory:
========================

Updated gajim package fixes security vulnerability:

Gajim before 0.16.5 doesnât verify the origin of roster pushes thus allowing
third parties to modify the roster via a man-in-the-middle attack
(CVE-2015-8688).

References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8688
http://gultsch.de/gajim_roster_push_and_message_interception.html
========================

Updated packages in core/updates_testing:
========================
python-nbxmpp-0.5.3-1.mga5
gajim-0.16.5-1.mga5

from SRPMS:
python-nbxmpp-0.5.3-1.mga5.src.rpm
gajim-0.16.5-1.mga5.src.rpm

Whiteboard: advisory feedback => advisory

Comment 5 Lewis Smith 2016-02-02 20:18:39 CET
Testing M5 x64
Updating also to: python-nbxmpp-0.5.3-1.mga5         [thanks David]
enabled Gajim to work (or not) the same as previously, so I am counting it OK.
FWIW The error I got when trying to send messages to myself was:
"error while sending <title> ( remote-server-not-found )".

Whiteboard: advisory => advisory MGA5-64-OK

Dave Hodgins 2016-02-05 03:49:37 CET

Keywords: (none) => validated_update
CC: (none) => davidwhodgins, sysadmin-bugs

Comment 6 Mageia Robot 2016-02-05 18:27:34 CET
An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGASA-2016-0046.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.