File: 3079.txt

package info (click to toggle)
snort 2.9.7.0-5
  • links: PTS, VCS
  • area: main
  • in suites: buster, 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,592 bytes parent folder | download | duplicates (8)
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:
3079

--
Summary:
This event is generated when an attempt is made to exploit a buffer
overflow associated with Microsoft's processing of an animated cursor
file.

--
Impact:
A successful attack may permit a buffer overflow that allows the execution
of arbitrary code at the privilege level of the user downloading the
malicious file.

--
Detailed Information:
A vulnerability exists in the way the Microsoft Windows LoadImage API validates
animated cursor (ANI) files. An invalid length associated with a structure
supporting the properties of the animated cursor can cause a buffer overflow
and the subsequent execution of arbirary code in the context of the current user.

--
Affected Systems:
	Windows 98, ME, NT, 2000, XP (not SP2), and Server 2003

--
Attack Scenarios:
An attacker can entice a user to download a malicious animated cursor
file, causing a buffer overflow and the subsequent execution of arbitrary
code on the vulnerable client.

--
Ease of Attack:
Simple.  Exploits exist.

--
False Positives:
None known.

--
False Negatives:
In order to avoid potential evasion techniques, http_inspect should be
configured with "flow_depth 0" so that all HTTP server response traffic is
inspected.

WARNING
Setting flow_depth 0 will cause performance problems in some situations.
WARNING

--
Corrective Action:
Apply the patch(s) discussed in Microsoft bulletin MS05-002.

--
Contributors:
Sourcefire Research Team
Judy Novak <judy.novak@sourcefire.com>

--
Additional References

Microsoft Technet:
http://www.microsoft.com/technet/security/bulletin/MS05-002.mspx

--