File: 1675.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 (70 lines) | stat: -rw-r--r-- 2,295 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
Rule:  

--
Sid: 1675

-- 

Summary: 
This event is generated when a command is issued to an Oracle database server that may result in a serious compromise of the data stored on that system.

-- 
Impact: 
Serious. An attacker may have gained superuser access to the system.

--
Detailed Information:
This event is generated when an attacker issues a special command to an Oracle database that may result in a serious compromise of all data stored on that system.

Such commands may be used to gain access to a system with the privileges of an administrator, delete data, add data, add users, delete users, return sensitive information or gain intelligence on the server software for further system compromise.
 
This connection can either be a legitimate telnet connection or the result of spawning a remote shell as a consequence of a successful network exploit. 

Oracle servers running on a Windows platform may listen on any arbitrary
port. Change the $ORACLE_PORTS variable in snort.conf to "any" if this
is applicable to the protected network.

--

Attack Scenarios: 
Simple. These are Oracle database commands.

-- 

Ease of Attack: 
Simple.

-- 

False Positives: 
This event may be generated by a database administrator logging in and issuing database commands from a location outside the protected network.

--
False Negatives:
Configure your ORACLE_PORTS variable correctly for the environment you are in. 
In many situations ORACLE negotiates a communication port. This means that 1521 
and 1526 are not used for communication during the entire transaction. A new 
port is negotiated after the initial connect message, all communication after 
that uses this other port. If you are in an environment such as this, you should 
set ORACLE_PORTS to "any" in snort.conf. 
 
Otherwise, there are no known false negatives.

-- 

Corrective Action: 
Use a firewall to disallow direct access to the Oracle database from sources external to the protected network.
Ensure that this event was not generated by a legitimate session then investigate the server for signs of compromise

Look for other events generated by the same IP addresses.

--
Contributors: 
Original Rule Writer Unknown
Sourcefire Research Team
Nigel Houghton <nigel.houghton@sourcefire.com>

-- 
Additional References:

--