File: 3068.txt

package info (click to toggle)
snort 2.9.2.2-3
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 53,752 kB
  • sloc: ansic: 214,625; sh: 13,872; makefile: 2,574; yacc: 505; perl: 496; lex: 260; sql: 213; sed: 14
file content (74 lines) | stat: -rw-r--r-- 1,813 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
Rule:

--
Sid:
3068

--
Summary:
This event is generated when an attempt is made to exploit a buffer
overflow associated with the several commands of an IMAP service. This
event is concerned with data supplied as a parameter to the
"examine" command.

--
Impact:
A successful attack may cause a denial of service or a buffer overflow
and the subsequent execution of arbitrary code on a vulnerable server.

--
Detailed Information:
This event is generated when excess data is detected in an IMAP command.
Some IMAP implementations exhibit programming errors that can lead to a
buffer overflow condition when excess data is supplied to a static
buffer.

A vulnerability exists in the way that the Mercury Mail IMAP service
handles several commands.  An excessively long command argument can
trigger a denial of service or a buffer overflow and the subsequent
execution of arbitrary code on a vulnerable server.

In the case of Ipswitch IMail, an overly long mailbox name supplied as a
parameter to the examine command may be a trigger condition of a buffer
overflow. A name of 259 bytes or more may cause this to occur.

--
Affected Systems:
	Pegasus Mail Mercury Mail Transport System 3.32
	Pegasus Mail Mercury Mail Transport System 4.01a
	Ipswitch IMail 8.1.3

--
Attack Scenarios:
An attacker can supplied an overly long command, causing denial of
service or a buffer overflow.

--
Ease of Attack:
Simple.

--
False Positives:
None known.

--
False Negatives:
None known.

--
Corrective Action:
Upgrade to the latest non-affected version of the software.

Apply the appropriate vendor supplied patches.

--
Contributors:
Sourcefire Vulnerability Research Team
Brian Caswell<bmc@sourcefire.com>
Judy Novak <judy.novak@sourcefire.com>
Nigel Houghton <nigel.houghton@sourcefire.com>

--
Additional References:

--