Bug 17325 - ruby-mail new security issue fixed upstream in 2.6.0
Summary: ruby-mail new security issue fixed upstream in 2.6.0
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
URL: http://lwn.net/Vulnerabilities/671471/
Whiteboard: MGA5-64-OK MGA5-32-OK advisory
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2015-12-11 19:27 CET by David Walser
Modified: 2016-01-15 02:53 CET (History)
4 users (show)

See Also:
Source RPM: ruby-mail-2.5.4-9.mga5.src.rpm
CVE:
Status comment:


Attachments
SMTP/Google test of ruby Mail class (1.50 KB, application/x-ruby)
2016-01-13 23:01 CET, Len Lawrence
Details

Description David Walser 2015-12-11 19:27:18 CET
A CVE was requested for an issue fixed in ruby-mail 2.6.0:
http://openwall.com/lists/oss-security/2015/12/11/3

The commit to fix the issue is linked in the message above.

Mageia 5 is also affected.

Reproducible: 

Steps to Reproduce:
David Walser 2015-12-11 19:27:24 CET

Whiteboard: (none) => MGA5TOO

Comment 1 David Walser 2016-01-11 21:31:10 CET
OpenSuSE has issued an advisory for this today (January 11):
http://lists.opensuse.org/opensuse-updates/2016-01/msg00013.html

The patch they used in this update can be found here:
https://build.opensuse.org/package/show/openSUSE:13.2:Update/rubygem-mail

URL: (none) => http://lwn.net/Vulnerabilities/671471/

Comment 2 David Walser 2016-01-12 00:48:09 CET
ruby-mail-2.6.3-1.mga6 uploaded for Cauldron for Pascal.

Patched package uploaded for Mageia 5.

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

Updated ruby-mail packages fix security vulnerability:

The Mail library does not impose a length limit on email addresses, so an
attacker can send a long spam message via a recipient address unless there is
a limit on the applicationâs side. The attacker-injected message in the
recipient address is processed by the server. This type of vulnerability can
be real threats in inquiry forms, member signup forms, or any other
application that delivers an email to a user-specified email address
(bsc#959129).

References:
http://openwall.com/lists/oss-security/2015/12/11/3
http://lists.opensuse.org/opensuse-updates/2016-01/msg00013.html
========================

Updated packages in core/updates_testing:
========================
ruby-mail-2.5.4-9.1.mga5
ruby-mail-doc-2.5.4-9.1.mga5

from ruby-mail-2.5.4-9.1.mga5.src.rpm

Whiteboard: MGA5TOO => (none)
Assignee: fundawang => qa-bugs
Version: Cauldron => 5

Comment 3 Herman Viaene 2016-01-13 10:39:38 CET
MGA5-32 Xfce on Acer D620
No installation issues.
I don't feel tempted to dive into ruby to put together some testcase, googling a minute didn't bring me any further. If the upper powers agree, then OK for me.

CC: (none) => herman.viaene

Comment 4 Len Lawrence 2016-01-13 11:16:31 CET
I will try to put together a test script for this but it will not be before tomorrow.  If it works I shall attach it and you can run it.  There seems to be a built-in test facility.  Later.

CC: (none) => tarazed25

Comment 5 Len Lawrence 2016-01-13 23:01:27 CET
Created attachment 7345 [details]
SMTP/Google test of ruby Mail class

Basic script for a user to send an email message back to self.  It is a bit specific and requires a username and password on the command line.
Comment 6 Len Lawrence 2016-01-13 23:04:14 CET
@Herman

I have uploaded a test script which simply transmits a message back to the user via gmail and SMTP.  You can override the SMTP setting by uncommenting the 'test' setting in the code.  If you are not using Google you might have to fiddle around with the SMTP settings, referring to the embedded URL which documents these things.  I am a bit out of my depth here.  In a browser the notes on SMTP can be found in the Class list index on the left.

You would have to edit the SMTP section of the script to set the password for the user.

Call the script whatever you like, e.g. mailtest.
$ chmod +x mailtest
<edit where necessary>
$ ./mailtest <user email address> <password>
or
$ ruby mailtest <email address> <password at Google or wherever>

I ran it before updating and picked up the email in Thunderbird a few seconds later.  Check the source and you see that the message id has been changed.

I hope it works for you.
Comment 7 Len Lawrence 2016-01-14 09:23:26 CET
Ignore the line in comment #6 about "You would have to edit the SMTP section....."
Comment 8 Len Lawrence 2016-01-14 18:58:32 CET
Since the 64-bit test succeeded for me I am going to pass it.
Len Lawrence 2016-01-14 18:58:57 CET

Whiteboard: (none) => MGA5-64-OK

Comment 9 Len Lawrence 2016-01-14 19:10:47 CET
mga5  i586 vbox  Mate

Installed the update candidate and sent an email to myself via Gmail and received it in Thunderbird on another machine.  Used the test script to exercise ruby-mail.
Len Lawrence 2016-01-14 19:11:08 CET

Whiteboard: MGA5-64-OK => MGA5-64-OK MGA5-32-OK

Len Lawrence 2016-01-14 19:11:23 CET

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

Comment 10 Thomas Backlund 2016-01-15 02:44:06 CET
 advisory added to svn

CC: (none) => tmb
Whiteboard: MGA5-64-OK MGA5-32-OK => MGA5-64-OK MGA5-32-OK advisory

Comment 11 Mageia Robot 2016-01-15 02:53:18 CET
An update for this issue has been pushed to Mageia Updates repository.

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

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


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