Bug 382204 - Certain Base64-encoded HTML messages cause composer to hit 100% CPU when attempting to reply
Summary: Certain Base64-encoded HTML messages cause composer to hit 100% CPU when atte...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.14.10
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-10 16:14 UTC by Mike Ely
Modified: 2017-07-15 02:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Ely 2017-07-10 16:14:16 UTC 
I'm trying to work out how to clean out confidential information from an example message while still including one that will cause the bug. In the meantime, the messages all come from our Veeam Backup and Replication server, so if anyone has access to one of those it should be easy enough to reproduce the bug. Just hit "Reply" to any message generated from same.

If anyone has advice on how to submit sufficient data to reproduce this bug while scrubbing confidential info I'm more than willing to do so.
Comment 1 Mike Ely 2017-07-10 16:15:58 UTC 
Sysinfo:
4.4.72-18.12-default #1 SMP Mon Jun 19 14:11:41 UTC 2017 (9c03296) x86_64 x86_64 x86_64 GNU/Linux
openSUSE 42.2 (x86_64)
i7-4790
Comment 2 Laurent Montel 2017-07-10 16:30:36 UTC 
4.4.10 is unmaintain.
Please try to test on last version 5.5.x (we will release 5.6.0 in 1 month)

Regards
Comment 3 Mike Ely 2017-07-10 16:59:21 UTC 
OK. I'll have to bug SuSE about this as I'm running the version that comes with their most-current stable distro. Thanks.
Comment 4 Mike Ely 2017-07-10 17:02:51 UTC 
I know resolved, but for my upstream-bothering could you please post a link indicating supported KMail versions and dates? I'd appreciate it.
Comment 5 Christoph Feck 2017-07-15 02:04:04 UTC 
Version - Release
5.6.0 - 2017.08 (next release)
5.5.3 - 2017.07 (current stable)
5.5.2 - 2017.06
5.5.1 - 2017.05
5.5.0 - 2017.04
5.4.3 - 2017.03 (previous stable)
5.4.2 - 2017.02
5.4.1 - 2017.01
5.4.0 - 2016.12
5.3.3 - 2016.11
.. and so on

The more recent your version is, the higher is the chance that someone looks at your tickets.