{"vuid":"VU#455323","idnumber":"455323","name":"Mandrake Security may make unexpected system modifications","keywords":["Mandrake Linux","Mandrake Security","msec","insecure permissions","home directory","default installation","755"],"overview":"The Mandrake Security utility included with Mandrake Linux may make unexpected modifications that affect system security.","clean_desc":"Mandrake Linux includes a tool named Mandrake Security (msec) that allows system administrators to manage and audit various system parameters associated with host security. These parameters include port-based access control, shell and console timeout values, user and root login policies, password maintenance, and system activity logging. System administrators may choose one of several preset security levels, then specify exceptions to these default policies. The CERT/CC has learned of a public report which states that the msec security level on a default installation of Mandrake Linux sets the file permissions of each user's home directory to mode 755, allowing full access to the directory owner, read-only access to group members, and read-only access to other users. In addition, the report alleges that if these settings are modified, the msec utility will restore the default settings during a periodic system audit. Although this utility may result in unexpected behavior, it appears that this behavior accurately maintains the configured security policy and is consistent with the product documentation. Given that the documentation is readily available and the utility allows system administrators to customize the behavior of msec, the CERT/CC does not believe that this utility represents a security vulnerability.","impact":"This utility accurately and consistently performs as documented. However, system administrators who do not understand its operation may encounter unexpected behavior.","resolution":"Read the msec documentation The CERT/CC encourages system administrators who wish to alter the default behavior of msec to read the product documentation and customize their msec configuration as appropriate.","workarounds":"","sysaffected":"","thanks":"This issue was reported to the Bugtraq mailing list by Spot on June 17, 2002.","author":"This document was written by Jeffrey P. Lanza.","public":["http://www.mandrakesecure.net/en/docs/msec.php","http://www.mandrakesecure.net/archives/discuss/2002-02/msg00277.html","http://www.securityfocus.com/bid/5050"],"cveids":[""],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2002-06-18T20:27:55Z","publicdate":"2002-06-17T00:00:00Z","datefirstpublished":"2002-06-25T20:21:33Z","dateupdated":"2002-06-25T21:58:27Z","revision":13,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"15","cam_exploitation":"10","cam_internetinfrastructure":"0","cam_population":"5","cam_impact":"4","cam_easeofexploitation":"4","cam_attackeraccessrequired":"5","cam_scorecurrent":"0.1875","cam_scorecurrentwidelyknown":"0.225","cam_scorecurrentwidelyknownexploited":"0.3","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":0.1875,"vulnote":null}