File: 1902.txt

package info (click to toggle)
snort 2.7.0-20.4
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 34,512 kB
  • ctags: 18,772
  • sloc: ansic: 115,404; sh: 10,893; makefile: 1,372; perl: 487; sql: 213
file content (66 lines) | stat: -rw-r--r-- 1,645 bytes parent folder | download | duplicates (4)
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
Rule:

--
Sid:
1902

--
Summary:
This event is generated when a remote attacker sends an IMAP LSUB
command with a malformed and overly long argument to an internal IMAP
server port. This may indicate an attempt to exploit a buffer overflow
vulnerability in the IMAP LSUB command.

--
Impact:
Possible shell access on the IMAP server, leading to arbitrary code
execution. The attacker must have a valid IMAP account on the mail
server to attempt this exploit.

--
Detailed Information:
When an LSUB command with an overly long argument is sent to a
vulnerable IMAP server, a buffer overflow condition may occur. This can
allow an attacker to execute arbitrary code from the command shell. Note
that this exploit can only be attempted by a user with a valid IMAP account.

--
Affected Systems:
	University of Washington imapd versions 10.234 or 12.264.

--
Attack Scenarios:
An attacker with an IMAP account on the server can send a sufficiently
long LSUB command to the IMAP server, creating a buffer overflow
condition. This can then allow the attacker to gain shell access on the
compromised server, possibly leading to the execution of arbitrary code.

--
Ease of Attack:
Simple. Exploits exist, but the user must have a valid IMAP account on
the server.

--
False Positives:
None known.

--
False Negatives:
None known.

--
Corrective Action:
Apply the patch for your current version of imapd appropriate to your
operating system.

--
Contributors:
Sourcefire Vulnerability Research Team
Brian Caswell <bmc@sourcefire.com>
Sourcefire Technical Publications Team
Jennifer Harvey <jennifer.harvey@sourcefire.com>

--
Additional References:

--