The registry in Windows NT can be accessed remotely by users who are not administrators.

IIS has the #exec function enabled for Server Side Include (SSI) files.

A system-critical Windows NT file or directory has inappropriate permissions.

A system-critical Unix file or directory has inappropriate permissions.

Two or more Unix accounts have the same UID.

A Unix account with a name other than "root" has UID 0, i.e. root privileges.

NFS exports system-critical data to the world, e.g. / or a password file.

HP OpenMail can be misconfigured to allow users to run arbitrary commands using malicious print requests.

A router's routing tables can be obtained from arbitrary hosts.

Windows NT automatically logs in an administrator upon rebooting.

A superfluous NFS server is running, but it is not importing or exporting any file systems.

An SSH server allows authentication through the .rhosts file.

The Windows NT guest account is enabled.

A password for accessing a WWW URL is guessable.

A trust relationship exists between two Unix hosts.

A configuration in a web browser such as Internet Explorer or Netscape Navigator allows execution of active content such as ActiveX, Java, Javascript, etc.

A Windows NT account policy for passwords has inappropriate, security-critical settings, e.g. for password length, password age, or uniqueness.

A Windows NT user has inappropriate rights or privileges, e.g. Act as System, Add Workstation, Backup, Change System Time, Create Pagefile, Create Permanent Object, Create Token Name, Debug, Generate Security Audit, Increase Priority, Increase Quota, Load Driver, Lock Memory, Profile Single Process, Remote Shutdown, Replace Process Token, Restore, System Environment, Take Ownership, or Unsolicited Input.

A DNS server allows inverse queries.

A DNS server allows zone transfers.