InterSystems Cache Insecure Default Permissions Vulnerability



Date Discovered

July 1, 2003


It has been reported that the permissions set by default on the files and directories comprising InterSystems Cache are insecure. The permissions on directories allegedly allow for any user to overwrite any file. This creates many opportunities for local attackers to obtain root privileges.

Technologies Affected

  • InterSystems Cache 4.1.15
  • InterSystems Cache 5.0.0
  • InterSystems Cache 5.0.1
  • InterSystems Cache 5.0.2


Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
This vulnerability requires local access to exploit. Do not provide user accounts on critical systems such as database servers to any but the most trusted individuals. If local access is necessary, use restricted shells or other mechanisms to prevent access to sensitive areas of the system.

Evaluate read, write, and execute permissions on all newly installed software.
Ensure that all software packages set permissions appropriately at install time. Change the permissions, if possible, if they do not. Doing so may prevent insecure default configurations such as this from being exploited by malicious local users.

The vendor has released versions 5.0.3 and 4.1.16 to address this issue. Please contact the vendor for further information on obtaining fixed versions of affected packages.



Discovered by Larry W. Cashdollar <>.

© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.