[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
Tiny Tiny RSS • PHPMailer Vulnerability CVE-2016-10033
Page 1 of 1

PHPMailer Vulnerability CVE-2016-10033

Posted: 26 Dec 2016, 21:19
by JustAMacUser
I'm on mobile so I haven't been able to investigate further with respect to TT-RSS or submit a patch, but since it uses an earlier version of PHPMailer I figured I should share this:



Based on how I think TT-RSS works, this should only be exploitable by registered users but nonetheless should probably be patched.

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 26 Dec 2016, 22:29
by fox
should be updated on gitlab, i tried the plugin and it worked but it would be good if someone tested other mail-related crap (i don't even remember - like, password reset links? something else?)

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 28 Dec 2016, 10:22
by derekschrock
Appears there's a follow up vulnerability to the original CVE-2016-10033. Additional updates to the embedded phpmailer might be needed?

https://legalhackers.com/advisories/PHP ... ypass.html

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 28 Dec 2016, 10:35
by fox
someone post here when that village idiot who couldn't figure out how to send email without executing random code updates his piece of shit library, so i can merge his new attempt into trunk, i guess

the anticipation is killing me

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 28 Dec 2016, 13:09
by virgo
I guess the problem only exists, if SMTP_SERVER is empty (so that mail is sent via system MTA).

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 28 Dec 2016, 13:19
by fox
yeah escapeshellargs() would do nothing for an smtp connection

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 29 Dec 2016, 05:26
by derekschrock

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 29 Dec 2016, 07:37
by fox
thanks, updated in trunk

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 04 Jan 2017, 00:16
by Mayhemer
The mail plugin seems to be broken, since PHPMailer has been updated. Also my own plugin, which sends mails like the mail plugin does, stopped working. How to use ttrssmailer now?

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 04 Jan 2017, 10:34
by fox
well first of all thanks for all the effort of providing no details or even error messages

second of all, https://tt-rss.org/gitlab/fox/tt-rss/co ... 7e356c2a27

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 04 Jan 2017, 12:04
by Mayhemer
Well, first of all, thanks for this very kind first contact. I am always happy being able to help ;-)
Second of all, I had 10 minutes time left and I used that to find a more or less appropriate thread to post the information. I had not enough time to investigate more, but I already wanted to tell you about the bug.
Third of all, if someone had asked about more details, I would have been happy to investigate more, when I have a few minutes left.
Fourth and most important of all, the information I provided was sufficient. :-)

My final question is: should I report a bug the next time, even if it is not perfectly investigated or should I avoid that?

PS: There is no offence intended from my side and I am more than happy about the work you do and the great software you provide.

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 16 Jan 2017, 16:21
by derekschrock
I guess this is our monthly update to phpmailer.

Can we get another update to phpmailer? https://github.com/PHPMailer/PHPMailer/ ... ag/v5.2.22

This addresses CVE-2017-5223

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 16 Jan 2017, 16:27
by fox
oh for fucks sake

e: someone please test if it works

Re: PHPMailer Vulnerability CVE-2016-10033

Posted: 16 Jan 2017, 16:47
by Mayhemer
Seems to work on my system. Also no suspicious log messages.
I tried the mail plugin and my kindle plugin. Both are working.