Page 2 of 6 results (0.003 seconds)

CVSS: 7.8EPSS: 0%CPEs: 1EXPL: 0

On Windows endpoints, the SecureConnector agent must run under the local SYSTEM account or another administrator account in order to enable full functionality of the agent. The typical configuration is for the agent to run as a Windows service under the local SYSTEM account. The SecureConnector agent runs various plugin scripts and executables on the endpoint in order to gather and report information about the host to the CounterACT management appliance. The SecureConnector agent downloads these scripts and executables as needed from the CounterACT management appliance and runs them on the endpoint. By default, these executable files are downloaded to and run from the %TEMP% directory of the currently logged on user, despite the fact that the SecureConnector agent is running as SYSTEM. • http://www.securityfocus.com/bid/94740 https://www.kb.cert.org/vuls/id/768331 • CWE-264: Permissions, Privileges, and Access Controls CWE-379: Creation of Temporary File in Directory with Insecure Permissions •