IpSwitch IMAP Server LOGON stack overflow

[Dave Aitel]

Neat! Although if you'd done the other Logon bug, you'd not have had to
worry about alpha-encoding quite so much, and you'd have a
SP-independant attack.

It's a good piece of artwork though. :>

-dave

Hello, attached is a proof of concept for the IpSwitch IMAP Server LOGON stack overflow
nolimit
------------------------------------------------------------------------
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

[Dave Aitel]

Hello dave, thanks for the reply. Feels good to have an established name in the security field
comment on my exploit as artwork :)
I did consider going after the STATUS overflow. This is the one you were talking about right? The
only downside is you need legit credentials for the mailserver first. While It's not too difficult
to brute force one, It just seemed easier to start on the LOGON one. As far as exploit writing
difficulty level, STATUS would have indeed been easier :>
nolimit

Perhaps I'm thinking of something else entirely, but looking here:
http://www.idefense.com/application/poi/display?id=243&type=vulnerabilities
I see them refering to the second bug, which is the one I wrote up for
CANVAS. You can pretty much auto-generate this without even loading ollydbg.

-dave

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

[n***@coreiso.org]

Hello dave, thanks for the reply. Feels good to have an established name in the security field
comment on my exploit as artwork :)

I did consider going after the STATUS overflow. This is the one you were talking about right? The
only downside is you need legit credentials for the mailserver first. While It's not too difficult
to brute force one, It just seemed easier to start on the LOGON one. As far as exploit writing
difficulty level, STATUS would have indeed been easier :>

nolimit

[n***@coreiso.org]

Ah, you refer to this one.
"The first vulnerability specifically exists in the handling of a long
username to the LOGIN command. A long username argument of approximately
2,000 bytes will cause a stack based unicode string buffer overflow
providing the attacker with partial control over EIP. As this
vulnerability is in the LOGIN command itself, valid credentials are not
required. "

Later it reads
"The second vulnerability also exists in the handling of the LOGIN
command username argument, however it lends itself to easier
exploitation."

I guess I shouldn't have trusted this statement :)
Perhaps I'll take a look at this one next, or just use your CANVAS example :)
Cheers
nolimit