Twenty Year Anniversary

iDEFENSE Security Advisory 2005-05-24.1

iDEFENSE Security Advisory 2005-05-24.1
Posted Aug 14, 2005
Authored by iDefense Labs | Site idefense.com

iDEFENSE Security Advisory 05.24.05-1 - Remote exploitation of a buffer overflow vulnerability in Ipswitch Inc.'s Imail 8.13 IMAP server allows attackers to execute arbitrary code with System privileges. The vulnerability specifically exists in the handling of a long mailbox name to the STATUS command. A long mailbox name argument will cause a stack based buffer overflow, providing the attacker with full control over the saved return address on the stack.

tags | advisory, remote, overflow, arbitrary, imap
advisories | CVE-2005-1256
MD5 | 2496ebe8bd4844748c4cb54571870a81

iDEFENSE Security Advisory 2005-05-24.1

Change Mirror Download
Ipswitch IMail IMAP STATUS Remote Buffer Overflow Vulnerability

iDEFENSE Security Advisory 05.24.05
www.idefense.com/application/poi/display?id=244&type=vulnerabilities
May 24, 2005

I. BACKGROUND

Ipswitch Collaboration Suite (ICS) is a comprehensive communication and
collaboration solution for Microsoft Windows with a customer base of
over 53 million users. More information is available on the vendor's
website:

http://www.ipswitch.com/products/IMail_Server/index.html

II. DESCRIPTION

Remote exploitation of a buffer overflow vulnerability in Ipswitch
Inc.'s Imail IMAP server allows attackers to execute arbitrary code with

System privileges.

The vulnerability specifically exists in the handling of a long mailbox
name to the STATUS command. A long mailbox name argument will cause a
stack based buffer overflow, providing the attacker with full control
over the saved return address on the stack. Once this has been achieved,

execution of arbitrary code becomes trivial. As this vulnerability is in

the STATUS command, which requires that a session is authenticated,
valid credentials are required.

III. ANALYSIS

Successful exploitation allows remote attackers to execute arbitrary
code with System privileges. Valid credentials are required for
exploitation, which lessens the impact of this vulnerability.

IV. DETECTION

iDEFENSE has confirmed the existence of this vulnerability in Ipswitch
IMail version 8.13. It is suspected that earlier versions are also
vulnerable.

V. WORKAROUND

As this vulnerability is exploited after authentication occurs, ensuring

that only trusted users have accounts can mitigate the risk somwhat. As
a more effective workaround, consider limiting access to the IMAP server

by filtering TCP port 143. If possible, consider disabling IMAP and
forcing users to use POP3.

VI. VENDOR RESPONSE

The vendor has released the following patch to fix this vulnerability:

ftp://ftp.ipswitch.com/Ipswitch/Product_Support/IMail/imail82hf2.exe

The associated vendor advisory can be found at:

http://www.ipswitch.com/support/imail/releases/imail_professional/im82hf
2.html

VII. CVE INFORMATION

The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CAN-2005-1256 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org), which standardizes names for
security problems.

VIII. DISCLOSURE TIMELINE

04/25/2005 Initial vendor notification
05/10/2005 Initial vendor response
05/24/2005 Public disclosure

IX. CREDIT

iDEFENSE Labs is credited with this discovery.

Get paid for vulnerability research
http://www.idefense.com/poi/teams/vcp.jsp

Free tools, research and upcoming events
http://labs.idefense.com

X. LEGAL NOTICES

Copyright (c) 2005 iDEFENSE, Inc.

Permission is granted for the redistribution of this alert
electronically. It may not be edited in any way without the express
written consent of iDEFENSE. If you wish to reprint the whole or any
part of this alert in any other medium other than electronically, please
email customerservice@idefense.com for permission.

Disclaimer: The information in the advisory is believed to be accurate
at the time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS condition.
There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct, indirect,
or consequential loss or damage arising from use of, or reliance on,
this information.

Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

Want To Donate?


Bitcoin: 18PFeCVLwpmaBuQqd5xAYZ8bZdvbyEWMmU

File Archive:

April 2018

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Apr 1st
    5 Files
  • 2
    Apr 2nd
    17 Files
  • 3
    Apr 3rd
    11 Files
  • 4
    Apr 4th
    21 Files
  • 5
    Apr 5th
    17 Files
  • 6
    Apr 6th
    12 Files
  • 7
    Apr 7th
    1 Files
  • 8
    Apr 8th
    6 Files
  • 9
    Apr 9th
    21 Files
  • 10
    Apr 10th
    18 Files
  • 11
    Apr 11th
    42 Files
  • 12
    Apr 12th
    7 Files
  • 13
    Apr 13th
    14 Files
  • 14
    Apr 14th
    1 Files
  • 15
    Apr 15th
    1 Files
  • 16
    Apr 16th
    15 Files
  • 17
    Apr 17th
    20 Files
  • 18
    Apr 18th
    24 Files
  • 19
    Apr 19th
    20 Files
  • 20
    Apr 20th
    7 Files
  • 21
    Apr 21st
    10 Files
  • 22
    Apr 22nd
    2 Files
  • 23
    Apr 23rd
    17 Files
  • 24
    Apr 24th
    36 Files
  • 25
    Apr 25th
    15 Files
  • 26
    Apr 26th
    31 Files
  • 27
    Apr 27th
    0 Files
  • 28
    Apr 28th
    0 Files
  • 29
    Apr 29th
    0 Files
  • 30
    Apr 30th
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2018 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close