File: group.yml

package info (click to toggle)
scap-security-guide 0.1.78-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 114,600 kB
  • sloc: xml: 245,305; sh: 84,381; python: 33,093; makefile: 27
file content (24 lines) | stat: -rw-r--r-- 942 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
documentation_complete: true

title: 'Ensure that No Dangerous Directories Exist in Root''s Path'

description: |-
    The active path of the root account can be obtained by
    starting a new root shell and running:
    <pre># echo $PATH</pre>
    This will produce a colon-separated list of
    directories in the path.
    <br /><br />
    Certain path elements could be considered dangerous, as they could lead
    to root executing unknown or
    untrusted programs, which could contain malicious
    code.
    Since root may sometimes work inside
    untrusted directories, the <tt>.</tt> character, which represents the
    current directory, should never be in the root path, nor should any
    directory which can be written to by an unprivileged or
    semi-privileged (system) user.
    <br /><br />
    It is a good practice for administrators to always execute
    privileged commands by typing the full path to the
    command.