During installation, installed file permissions are set to allow anyone to modify those files.
The architecture needs to access and modification attributes for files to only those users who actually require those actions.
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide...
According to SOAR [REF-1479], the following detection techniques may be useful:
According to SOAR [REF-1479], the following detection techniques may be useful:
According to SOAR [REF-1479], the following detection techniques may be useful:
According to SOAR [REF-1479], the following detection techniques may be useful:
According to SOAR [REF-1479], the following detection techniques may be useful:
According to SOAR [REF-1479], the following detection techniques may be useful:
According to SOAR [REF-1479], the following detection techniques may be useful:
According to SOAR [REF-1479], the following detection techniques may be useful:
CVE-2005-1941Executables installed world-writable.
CVE-2002-1713Home directories installed world-readable.
CVE-2001-1550World-writable log files allow information loss; world-readable file has cleartext passwords.
CVE-2002-1711World-readable directory.
CVE-2002-1844Windows product uses insecure permissions when installing on Solaris (genesis: port error).