Commit | Line | Data |
---|---|---|
a0d0e21e LW |
1 | =head1 NAME |
2 | ||
3 | perlsec - Perl security | |
4 | ||
5 | =head1 DESCRIPTION | |
6 | ||
425e5e39 | 7 | Perl is designed to make it easy to program securely even when running |
8 | with extra privileges, like setuid or setgid programs. Unlike most | |
54310121 | 9 | command line shells, which are based on multiple substitution passes on |
425e5e39 | 10 | each line of the script, Perl uses a more conventional evaluation scheme |
11 | with fewer hidden snags. Additionally, because the language has more | |
54310121 | 12 | builtin functionality, it can rely less upon external (and possibly |
425e5e39 | 13 | untrustworthy) programs to accomplish its purposes. |
a0d0e21e | 14 | |
425e5e39 | 15 | Perl automatically enables a set of special security checks, called I<taint |
16 | mode>, when it detects its program running with differing real and effective | |
17 | user or group IDs. The setuid bit in Unix permissions is mode 04000, the | |
18 | setgid bit mode 02000; either or both may be set. You can also enable taint | |
5f05dabc | 19 | mode explicitly by using the B<-T> command line flag. This flag is |
425e5e39 | 20 | I<strongly> suggested for server programs and any program run on behalf of |
fb73857a | 21 | someone else, such as a CGI script. Once taint mode is on, it's on for |
22 | the remainder of your script. | |
a0d0e21e | 23 | |
1e422769 | 24 | While in this mode, Perl takes special precautions called I<taint |
25 | checks> to prevent both obvious and subtle traps. Some of these checks | |
26 | are reasonably simple, such as verifying that path directories aren't | |
27 | writable by others; careful programmers have always used checks like | |
28 | these. Other checks, however, are best supported by the language itself, | |
fb73857a | 29 | and it is these checks especially that contribute to making a set-id Perl |
425e5e39 | 30 | program more secure than the corresponding C program. |
31 | ||
fb73857a | 32 | You may not use data derived from outside your program to affect |
33 | something else outside your program--at least, not by accident. All | |
34 | command line arguments, environment variables, locale information (see | |
d929ce6f | 35 | L<perllocale>), results of certain system calls (readdir(), |
41d6edb2 JH |
36 | readlink(), the variable of shmread(), the messages returned by |
37 | msgrcv(), the password, gcos and shell fields returned by the | |
38 | getpwxxx() calls), and all file input are marked as "tainted". | |
39 | Tainted data may not be used directly or indirectly in any command | |
40 | that invokes a sub-shell, nor in any command that modifies files, | |
b7ee89ce AP |
41 | directories, or processes, B<with the following exceptions>: |
42 | ||
43 | =over 4 | |
44 | ||
45 | =item * | |
46 | ||
47 | If you pass a list of arguments to either C<system> or C<exec>, | |
48 | the elements of that list are B<not> checked for taintedness. | |
49 | ||
50 | =item * | |
51 | ||
52 | Arguments to C<print> and C<syswrite> are B<not> checked for taintedness. | |
53 | ||
54 | =back | |
55 | ||
56 | Any variable set to a value | |
41d6edb2 | 57 | derived from tainted data will itself be tainted, even if it is |
d929ce6f JH |
58 | logically impossible for the tainted data to alter the variable. |
59 | Because taintedness is associated with each scalar value, some | |
60 | elements of an array can be tainted and others not. | |
a0d0e21e | 61 | |
a0d0e21e LW |
62 | For example: |
63 | ||
425e5e39 | 64 | $arg = shift; # $arg is tainted |
65 | $hid = $arg, 'bar'; # $hid is also tainted | |
66 | $line = <>; # Tainted | |
8ebc5c01 | 67 | $line = <STDIN>; # Also tainted |
68 | open FOO, "/home/me/bar" or die $!; | |
69 | $line = <FOO>; # Still tainted | |
a0d0e21e | 70 | $path = $ENV{'PATH'}; # Tainted, but see below |
425e5e39 | 71 | $data = 'abc'; # Not tainted |
a0d0e21e | 72 | |
425e5e39 | 73 | system "echo $arg"; # Insecure |
74 | system "/bin/echo", $arg; # Secure (doesn't use sh) | |
75 | system "echo $hid"; # Insecure | |
76 | system "echo $data"; # Insecure until PATH set | |
a0d0e21e | 77 | |
425e5e39 | 78 | $path = $ENV{'PATH'}; # $path now tainted |
a0d0e21e | 79 | |
54310121 | 80 | $ENV{'PATH'} = '/bin:/usr/bin'; |
c90c0ff4 | 81 | delete @ENV{'IFS', 'CDPATH', 'ENV', 'BASH_ENV'}; |
a0d0e21e | 82 | |
425e5e39 | 83 | $path = $ENV{'PATH'}; # $path now NOT tainted |
84 | system "echo $data"; # Is secure now! | |
a0d0e21e | 85 | |
425e5e39 | 86 | open(FOO, "< $arg"); # OK - read-only file |
87 | open(FOO, "> $arg"); # Not OK - trying to write | |
a0d0e21e | 88 | |
425e5e39 | 89 | open(FOO,"echo $arg|"); # Not OK, but... |
90 | open(FOO,"-|") | |
91 | or exec 'echo', $arg; # OK | |
a0d0e21e | 92 | |
425e5e39 | 93 | $shout = `echo $arg`; # Insecure, $shout now tainted |
a0d0e21e | 94 | |
425e5e39 | 95 | unlink $data, $arg; # Insecure |
96 | umask $arg; # Insecure | |
a0d0e21e | 97 | |
425e5e39 | 98 | exec "echo $arg"; # Insecure |
99 | exec "echo", $arg; # Secure (doesn't use the shell) | |
100 | exec "sh", '-c', $arg; # Considered secure, alas! | |
a0d0e21e | 101 | |
3a4b19e4 GS |
102 | @files = <*.c>; # insecure (uses readdir() or similar) |
103 | @files = glob('*.c'); # insecure (uses readdir() or similar) | |
7bac28a0 | 104 | |
a0d0e21e | 105 | If you try to do something insecure, you will get a fatal error saying |
62f468fc | 106 | something like "Insecure dependency" or "Insecure $ENV{PATH}". Note that you |
425e5e39 | 107 | can still write an insecure B<system> or B<exec>, but only by explicitly |
a3cb178b | 108 | doing something like the "considered secure" example above. |
425e5e39 | 109 | |
110 | =head2 Laundering and Detecting Tainted Data | |
111 | ||
112 | To test whether a variable contains tainted data, and whose use would thus | |
fb73857a | 113 | trigger an "Insecure dependency" message, check your nearby CPAN mirror |
114 | for the F<Taint.pm> module, which should become available around November | |
115 | 1997. Or you may be able to use the following I<is_tainted()> function. | |
425e5e39 | 116 | |
117 | sub is_tainted { | |
54310121 | 118 | return ! eval { |
119 | join('',@_), kill 0; | |
120 | 1; | |
425e5e39 | 121 | }; |
122 | } | |
123 | ||
124 | This function makes use of the fact that the presence of tainted data | |
125 | anywhere within an expression renders the entire expression tainted. It | |
126 | would be inefficient for every operator to test every argument for | |
127 | taintedness. Instead, the slightly more efficient and conservative | |
128 | approach is used that if any tainted value has been accessed within the | |
129 | same expression, the whole expression is considered tainted. | |
130 | ||
5f05dabc | 131 | But testing for taintedness gets you only so far. Sometimes you have just |
425e5e39 | 132 | to clear your data's taintedness. The only way to bypass the tainting |
54310121 | 133 | mechanism is by referencing subpatterns from a regular expression match. |
425e5e39 | 134 | Perl presumes that if you reference a substring using $1, $2, etc., that |
135 | you knew what you were doing when you wrote the pattern. That means using | |
136 | a bit of thought--don't just blindly untaint anything, or you defeat the | |
a034a98d DD |
137 | entire mechanism. It's better to verify that the variable has only good |
138 | characters (for certain values of "good") rather than checking whether it | |
139 | has any bad characters. That's because it's far too easy to miss bad | |
140 | characters that you never thought of. | |
425e5e39 | 141 | |
142 | Here's a test to make sure that the data contains nothing but "word" | |
143 | characters (alphabetics, numerics, and underscores), a hyphen, an at sign, | |
144 | or a dot. | |
145 | ||
54310121 | 146 | if ($data =~ /^([-\@\w.]+)$/) { |
425e5e39 | 147 | $data = $1; # $data now untainted |
148 | } else { | |
149 | die "Bad data in $data"; # log this somewhere | |
150 | } | |
151 | ||
5f05dabc | 152 | This is fairly secure because C</\w+/> doesn't normally match shell |
425e5e39 | 153 | metacharacters, nor are dot, dash, or at going to mean something special |
154 | to the shell. Use of C</.+/> would have been insecure in theory because | |
155 | it lets everything through, but Perl doesn't check for that. The lesson | |
156 | is that when untainting, you must be exceedingly careful with your patterns. | |
19799a22 | 157 | Laundering data using regular expression is the I<only> mechanism for |
425e5e39 | 158 | untainting dirty data, unless you use the strategy detailed below to fork |
159 | a child of lesser privilege. | |
160 | ||
a034a98d DD |
161 | The example does not untaint $data if C<use locale> is in effect, |
162 | because the characters matched by C<\w> are determined by the locale. | |
163 | Perl considers that locale definitions are untrustworthy because they | |
164 | contain data from outside the program. If you are writing a | |
165 | locale-aware program, and want to launder data with a regular expression | |
166 | containing C<\w>, put C<no locale> ahead of the expression in the same | |
167 | block. See L<perllocale/SECURITY> for further discussion and examples. | |
168 | ||
3a52c276 CS |
169 | =head2 Switches On the "#!" Line |
170 | ||
171 | When you make a script executable, in order to make it usable as a | |
172 | command, the system will pass switches to perl from the script's #! | |
54310121 | 173 | line. Perl checks that any command line switches given to a setuid |
3a52c276 | 174 | (or setgid) script actually match the ones set on the #! line. Some |
54310121 | 175 | Unix and Unix-like environments impose a one-switch limit on the #! |
3a52c276 | 176 | line, so you may need to use something like C<-wU> instead of C<-w -U> |
54310121 | 177 | under such systems. (This issue should arise only in Unix or |
178 | Unix-like environments that support #! and setuid or setgid scripts.) | |
3a52c276 | 179 | |
425e5e39 | 180 | =head2 Cleaning Up Your Path |
181 | ||
1fef88e7 | 182 | For "Insecure C<$ENV{PATH}>" messages, you need to set C<$ENV{'PATH'}> to a |
1e422769 | 183 | known value, and each directory in the path must be non-writable by others |
184 | than its owner and group. You may be surprised to get this message even | |
185 | if the pathname to your executable is fully qualified. This is I<not> | |
186 | generated because you didn't supply a full path to the program; instead, | |
187 | it's generated because you never set your PATH environment variable, or | |
188 | you didn't set it to something that was safe. Because Perl can't | |
189 | guarantee that the executable in question isn't itself going to turn | |
190 | around and execute some other program that is dependent on your PATH, it | |
54310121 | 191 | makes sure you set the PATH. |
a0d0e21e | 192 | |
a3cb178b GS |
193 | The PATH isn't the only environment variable which can cause problems. |
194 | Because some shells may use the variables IFS, CDPATH, ENV, and | |
195 | BASH_ENV, Perl checks that those are either empty or untainted when | |
196 | starting subprocesses. You may wish to add something like this to your | |
197 | setid and taint-checking scripts. | |
198 | ||
199 | delete @ENV{qw(IFS CDPATH ENV BASH_ENV)}; # Make %ENV safer | |
200 | ||
a0d0e21e LW |
201 | It's also possible to get into trouble with other operations that don't |
202 | care whether they use tainted values. Make judicious use of the file | |
203 | tests in dealing with any user-supplied filenames. When possible, do | |
fb73857a | 204 | opens and such B<after> properly dropping any special user (or group!) |
205 | privileges. Perl doesn't prevent you from opening tainted filenames for reading, | |
a0d0e21e LW |
206 | so be careful what you print out. The tainting mechanism is intended to |
207 | prevent stupid mistakes, not to remove the need for thought. | |
208 | ||
425e5e39 | 209 | Perl does not call the shell to expand wild cards when you pass B<system> |
210 | and B<exec> explicit parameter lists instead of strings with possible shell | |
211 | wildcards in them. Unfortunately, the B<open>, B<glob>, and | |
54310121 | 212 | backtick functions provide no such alternate calling convention, so more |
213 | subterfuge will be required. | |
425e5e39 | 214 | |
215 | Perl provides a reasonably safe way to open a file or pipe from a setuid | |
216 | or setgid program: just create a child process with reduced privilege who | |
217 | does the dirty work for you. First, fork a child using the special | |
218 | B<open> syntax that connects the parent and child by a pipe. Now the | |
219 | child resets its ID set and any other per-process attributes, like | |
220 | environment variables, umasks, current working directories, back to the | |
221 | originals or known safe values. Then the child process, which no longer | |
222 | has any special permissions, does the B<open> or other system call. | |
223 | Finally, the child passes the data it managed to access back to the | |
5f05dabc | 224 | parent. Because the file or pipe was opened in the child while running |
425e5e39 | 225 | under less privilege than the parent, it's not apt to be tricked into |
226 | doing something it shouldn't. | |
227 | ||
54310121 | 228 | Here's a way to do backticks reasonably safely. Notice how the B<exec> is |
425e5e39 | 229 | not called with a string that the shell could expand. This is by far the |
230 | best way to call something that might be subjected to shell escapes: just | |
fb73857a | 231 | never call the shell at all. |
cb1a09d0 | 232 | |
54310121 | 233 | use English; |
fb73857a | 234 | die "Can't fork: $!" unless defined $pid = open(KID, "-|"); |
cb1a09d0 AD |
235 | if ($pid) { # parent |
236 | while (<KID>) { | |
237 | # do something | |
425e5e39 | 238 | } |
cb1a09d0 AD |
239 | close KID; |
240 | } else { | |
fb73857a | 241 | my @temp = ($EUID, $EGID); |
425e5e39 | 242 | $EUID = $UID; |
5a964f20 | 243 | $EGID = $GID; # initgroups() also called! |
fb73857a | 244 | # Make sure privs are really gone |
245 | ($EUID, $EGID) = @temp; | |
5a964f20 TC |
246 | die "Can't drop privileges" |
247 | unless $UID == $EUID && $GID eq $EGID; | |
425e5e39 | 248 | $ENV{PATH} = "/bin:/usr/bin"; |
5a964f20 TC |
249 | exec 'myprog', 'arg1', 'arg2' |
250 | or die "can't exec myprog: $!"; | |
425e5e39 | 251 | } |
252 | ||
fb73857a | 253 | A similar strategy would work for wildcard expansion via C<glob>, although |
254 | you can use C<readdir> instead. | |
425e5e39 | 255 | |
256 | Taint checking is most useful when although you trust yourself not to have | |
257 | written a program to give away the farm, you don't necessarily trust those | |
258 | who end up using it not to try to trick it into doing something bad. This | |
fb73857a | 259 | is the kind of security checking that's useful for set-id programs and |
425e5e39 | 260 | programs launched on someone else's behalf, like CGI programs. |
261 | ||
262 | This is quite different, however, from not even trusting the writer of the | |
263 | code not to try to do something evil. That's the kind of trust needed | |
264 | when someone hands you a program you've never seen before and says, "Here, | |
265 | run this." For that kind of safety, check out the Safe module, | |
266 | included standard in the Perl distribution. This module allows the | |
267 | programmer to set up special compartments in which all system operations | |
268 | are trapped and namespace access is carefully controlled. | |
269 | ||
270 | =head2 Security Bugs | |
271 | ||
272 | Beyond the obvious problems that stem from giving special privileges to | |
fb73857a | 273 | systems as flexible as scripts, on many versions of Unix, set-id scripts |
425e5e39 | 274 | are inherently insecure right from the start. The problem is a race |
275 | condition in the kernel. Between the time the kernel opens the file to | |
fb73857a | 276 | see which interpreter to run and when the (now-set-id) interpreter turns |
425e5e39 | 277 | around and reopens the file to interpret it, the file in question may have |
278 | changed, especially if you have symbolic links on your system. | |
279 | ||
280 | Fortunately, sometimes this kernel "feature" can be disabled. | |
281 | Unfortunately, there are two ways to disable it. The system can simply | |
fb73857a | 282 | outlaw scripts with any set-id bit set, which doesn't help much. |
283 | Alternately, it can simply ignore the set-id bits on scripts. If the | |
425e5e39 | 284 | latter is true, Perl can emulate the setuid and setgid mechanism when it |
285 | notices the otherwise useless setuid/gid bits on Perl scripts. It does | |
286 | this via a special executable called B<suidperl> that is automatically | |
54310121 | 287 | invoked for you if it's needed. |
425e5e39 | 288 | |
fb73857a | 289 | However, if the kernel set-id script feature isn't disabled, Perl will |
290 | complain loudly that your set-id script is insecure. You'll need to | |
291 | either disable the kernel set-id script feature, or put a C wrapper around | |
425e5e39 | 292 | the script. A C wrapper is just a compiled program that does nothing |
293 | except call your Perl program. Compiled programs are not subject to the | |
fb73857a | 294 | kernel bug that plagues set-id scripts. Here's a simple wrapper, written |
425e5e39 | 295 | in C: |
296 | ||
297 | #define REAL_PATH "/path/to/script" | |
54310121 | 298 | main(ac, av) |
425e5e39 | 299 | char **av; |
300 | { | |
301 | execv(REAL_PATH, av); | |
54310121 | 302 | } |
cb1a09d0 | 303 | |
54310121 | 304 | Compile this wrapper into a binary executable and then make I<it> rather |
305 | than your script setuid or setgid. | |
425e5e39 | 306 | |
425e5e39 | 307 | In recent years, vendors have begun to supply systems free of this |
308 | inherent security bug. On such systems, when the kernel passes the name | |
fb73857a | 309 | of the set-id script to open to the interpreter, rather than using a |
425e5e39 | 310 | pathname subject to meddling, it instead passes I</dev/fd/3>. This is a |
311 | special file already opened on the script, so that there can be no race | |
312 | condition for evil scripts to exploit. On these systems, Perl should be | |
313 | compiled with C<-DSETUID_SCRIPTS_ARE_SECURE_NOW>. The B<Configure> | |
314 | program that builds Perl tries to figure this out for itself, so you | |
315 | should never have to specify this yourself. Most modern releases of | |
316 | SysVr4 and BSD 4.4 use this approach to avoid the kernel race condition. | |
317 | ||
0325b4c4 JH |
318 | Prior to release 5.6.1 of Perl, bugs in the code of B<suidperl> could |
319 | introduce a security hole. | |
68dc0745 | 320 | |
321 | =head2 Protecting Your Programs | |
322 | ||
323 | There are a number of ways to hide the source to your Perl programs, | |
324 | with varying levels of "security". | |
325 | ||
326 | First of all, however, you I<can't> take away read permission, because | |
327 | the source code has to be readable in order to be compiled and | |
328 | interpreted. (That doesn't mean that a CGI script's source is | |
329 | readable by people on the web, though.) So you have to leave the | |
5a964f20 TC |
330 | permissions at the socially friendly 0755 level. This lets |
331 | people on your local system only see your source. | |
68dc0745 | 332 | |
5a964f20 | 333 | Some people mistakenly regard this as a security problem. If your program does |
68dc0745 | 334 | insecure things, and relies on people not knowing how to exploit those |
335 | insecurities, it is not secure. It is often possible for someone to | |
336 | determine the insecure things and exploit them without viewing the | |
337 | source. Security through obscurity, the name for hiding your bugs | |
338 | instead of fixing them, is little security indeed. | |
339 | ||
340 | You can try using encryption via source filters (Filter::* from CPAN). | |
341 | But crackers might be able to decrypt it. You can try using the | |
54310121 | 342 | byte code compiler and interpreter described below, but crackers might |
68dc0745 | 343 | be able to de-compile it. You can try using the native-code compiler |
344 | described below, but crackers might be able to disassemble it. These | |
345 | pose varying degrees of difficulty to people wanting to get at your | |
346 | code, but none can definitively conceal it (this is true of every | |
347 | language, not just Perl). | |
348 | ||
349 | If you're concerned about people profiting from your code, then the | |
350 | bottom line is that nothing but a restrictive licence will give you | |
351 | legal security. License your software and pepper it with threatening | |
352 | statements like "This is unpublished proprietary software of XYZ Corp. | |
353 | Your access to it does not give you permission to use it blah blah | |
354 | blah." You should see a lawyer to be sure your licence's wording will | |
355 | stand up in court. | |
5a964f20 TC |
356 | |
357 | =head1 SEE ALSO | |
358 | ||
359 | L<perlrun> for its description of cleaning up environment variables. |