[Dovecot] Bug? High CPU Usage after nessus scan

[Jens Gutzeit]

Hi all,

I think I've found a Bug in current rc2 (same occours with rc1 and
0.99.9.1).

I'am running dovecot with imap, pop3 and the ssl equivalents, after a
nessus scan of my host with Bruteforce checks on IMAP, imap-login eats
up lots of cpu.

Before the scan:

dovecot  22342  0.0  0.1  2320  636 ?      SN   Jun18  0:00 imap-login
dovecot   5841  0.0  0.1  2320  692 ?      SN   Jun21  0:00 imap-login
dovecot   5852  0.0  0.1  2320  692 ?      SN   Jun21  0:00 imap-login

Looks wonderfull ;)

After the scan:

dovecot  20059 39.5  0.2  2340  820 ?     RN  20:02  14:08 imap-login
dovecot  20733  0.0  0.2  2320  804 ?     SN  20:03  0:00 imap-login
dovecot  20734  0.0  0.2  2320  804 ?     SN  20:03  0:00 imap-login
dovecot  20780 41.3  0.2  2340  820 ?     RN  20:03 14:04 imap-login
dovecot  20855  0.0  0.2  2320  804 ?     SN  20:04   0:00 imap-login

This was on my local test machine, the same occours on a production
machine, both are running Debian GNU/Linux woody, one with Openssl and
one with GNUTLS.

Even 2 hours after the scan the CPU Usage is so high, I don't think this
is normal behaviour?

The logs didn't say anything during the test. If you need more
information please tell me what data you need and I look for it.

-- 
Best regards/freundliche Grüße
Jens Gutzeit 
http://www.gutzeit.at