File: 2119.txt

package info (click to toggle)
snort 2.9.7.0-5
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid, stretch
  • size: 55,000 kB
  • ctags: 38,464
  • sloc: ansic: 266,667; sh: 12,508; makefile: 2,908; yacc: 497; perl: 496; lex: 261; sed: 14
file content (69 lines) | stat: -rw-r--r-- 1,765 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
67
68
69
Rule:

--
Sid:
2119

--
Summary:
This event is generated when a remote user uses the IMAP RENAME command
to send a suspiciously long string to port 143 on an internal server.
This may indicate an attempt to exploit a buffer overflow vulnerability
in the IMAP RENAME command. This may also affect other IMAP implementations.

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 a large amount of data is sent to a vulnerable IMAP server in the
RENAME command, a buffer overflow condition may occur. This can allow
the attacker to access the shell, where arbitrary code can be executed.
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 RENAME 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:
Upgrade to the latest non-affected version of the software.

Apply the appropriate patches for your operating system.

Check the host for signs of compromise.

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

--
Additional References:

--