Debian Codegraph @

doc/README.NTSecurity

raw
1 Issue:
2 ======
3 If the LocalSystem user is allowed to install the Firebird Service,
4 it could make the whole system accessible to a malicious attacker.
5
6 Scope:
7 ======
8 Affects Windows NT platforms.
9
10 Document author:
11 =================
12 Alex Peshkov ([email protected])
13
14 Document date: 2003/06/22
15 ==============
16
17
18 Firebird installation kits for Windows NT systems, i.e. those that
19 support services, currently provide a route into the host system
20 for any hacker who finds a new security hole in Firebird. All of
21 the current kits install the Firebird service to run under the
22 LocalSystem account. Through Firebird, the attacker can get
23 LocalSystem access to the system.
24
25 The steps to fix things manually are simple:
26
27 1) add the user 'firebird' as a member of the Domain users group,
28 with default rights
29
30 2) grant this user write access to all databases, including
31 security2.fdb (isc4.gdb in pre-1.5 versions), and the
32 firebird.log file
33
34 3) grant the user 'firebird' rights to "Login as service"
35
36 4) make the Firebird services (FirebirdServer and FirebirdGuardian,
37 if used, log in with username 'firebird'
38
39 Solution:
40 =========
41 Alex Peshkov
42
43 People writing installers should note that Firebird's standard routine
44 to install and manage the Firebird Service on WinNT/2000/XP platforms
45 (instsvc.exe) was upgraded in version 1.5 by the addition of an
46 optional L[ogin] switch to the {install} command. It is strongly
47 recommended that you employ this switch in the Windows kits, to make
48 the 'firebird' user, not LocalSystem, the default account under which
49 the Firebird Service logs in.
50
51 For more details, see the document README.instsvc
52 switch to (see instsvc.exe).