{"id":586,"date":"2011-07-18T01:15:02","date_gmt":"2011-07-17T23:15:02","guid":{"rendered":"http:\/\/blog.blackdown.de\/?p=586"},"modified":"2016-10-29T03:50:59","modified_gmt":"2016-10-29T01:50:59","slug":"os-x-applications-insecurely-installing-world-writable-files","status":"publish","type":"post","link":"https:\/\/blackdown.de\/articles\/os-x-applications-insecurely-installing-world-writable-files\/","title":{"rendered":"OS X Applications Insecurely Installing World-Writable Files"},"content":{"rendered":"

Files, directories, and devices that are writable by any user (“world-writable”) on a multi-user system can be dangerous locally exploitable security holes. There are very few legitimate reasons for having world-writable files and directories on a system.<\/p>\n

Many UNIX and Linux systems actually have cron<\/em> jobs that check for world-writable files. On Apple’s OS X there is no such safeguard and many vendors do not seem to care about file permissions much at all. Several well-known applications are either installed with world-writable files or create them when used:<\/p>\n

World-writable files in system directories<\/h4>\n

The following applications install world-writable files in shared directories (\/Applications<\/code>, \/Library<\/code>, …):<\/p>\n