File: 2183.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 (71 lines) | stat: -rw-r--r-- 1,605 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
Rule:

--
Sid:
2183

--
Summary:
This event is generated when an attempt is made to exploit a known 
vulnerability in certain versions of Sendmail.

--
Impact:
Denial of Service (DoS), possible arbitrary code execution and the 
remote attacker can gain access to a machine with the credentials of
the user running the Sendmail daemon, usually 'root'.

--
Detailed Information:
A vulnerability exists in the Sendmail MTA Daemon that could allow an
attacker the opportunity to gain root access.

A programming error exists such that a buffer overflow can be caused
using the header fields in an SMTP session. The prescan() function does 
not properly handle certain conversions from character and integer 
types. This can cause Sendmail to interpret the value as a special 
control value (NOCHAR).

This rule detects specific exploit code attacks against a server using 
Sendmail.

--
Affected Systems:
	Sendmail Pro (all versions)
	Sendmail Switch 2.1 prior to 2.1.6
	Sendmail Switch 2.2 prior to 2.2.6
	Sendmail Switch 3.0 prior to 3.0.4
	Sendmail for NT 2.X prior to 2.6.3
	Sendmail for NT 3.0 prior to 3.0.4
	Systems running open-source sendmail versions prior to 8.12.9, including UNIX and Linux systems

--
Attack Scenarios:
The attacker merely needs to execute one of the available exploit 
scripts.

--
Ease of Attack:
Simple. Exploits for this vulnerability exist.

--
False Positives:
None Known.

--
False Negatives:
None Known.

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

Apply the appropriate vendor supplied patches.

--
Contributors:

--
Additional References:

--