{"vuid":"VU#204232","idnumber":"204232","name":"Up.time agent for Linux does not authenticate a user before allowing read access to the file system","keywords":["authentication","linux","CWE-306"],"overview":"The up.time agent for Linux versions 7.5 and 7.6 may allow an unauthenticated remote attacker to read arbitrary files from a system.","clean_desc":"CWE-306: Missing Authentication for Critical Function - CVE-2015-8268 According to the researcher, \"The linux based uptime.agent version 7.5 provides the ability to remotely read any file on the remote system that the uptime.agent has read access to, without authentication.\" Idera has identified that versions 7.5 and 7.6 are affected. Related vulnerabilities were initially reported in VU#377260.","impact":"An unauthenticated remote user may be able to read arbitrary files from a system running the Up.time agent for Linux.","resolution":"Apply an update Idera has released Up.time version 7.7 which addresses this issue. Affected users are encouraged to update to the latest available version as soon as possible. Affected users should also consider the following mitigations for this and other vulnerabilities.","workarounds":"Check configuration According to Idera, affected users may also use the following configuration settings to mitigate these issues: 1. All agents run in a read only mode by default, where they can only poll metrics. 2. In order to use custom scripts or trigger recovery actions, you need to set a password on the agent, or add commands to the .uptmpasswd file for the linux agent. 3. Agents communication can be encrypted with SSL by using various SSL Tunneling/Proxy Utilities (openSSL, etc). KB articles cover the specifics for implementing with Stunnel on various platforms. 4. Agents running under xinet.d can also be secured at the service level by restricting incoming connections to only accept connections from the Monitoring Station, or limit the total number of connections, etc. 5. Disable Agent Commands you don't use either via the Agent Console or editing conf/agent_commands.txt.","sysaffected":"","thanks":"Thanks to Ryan Wincey for reporting this vulnerability.","author":"This document was written by Garret Wassermann.","public":["http://docs.uptimesoftware.com/display/UT/Release+Notes","http://jira.uptimesoftware.com/browse/UT-16039"],"cveids":["CVE-2015-8268"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2015-10-28T16:23:06Z","publicdate":"2016-05-11T00:00:00Z","datefirstpublished":"2016-05-19T15:18:39Z","dateupdated":"2016-06-14T15:04:58Z","revision":31,"vrda_d1_directreport":"1","vrda_d1_population":"2","vrda_d1_impact":"2","cam_widelyknown":"0","cam_exploitation":"0","cam_internetinfrastructure":"0","cam_population":"0","cam_impact":"0","cam_easeofexploitation":"0","cam_attackeraccessrequired":"0","cam_scorecurrent":"0","cam_scorecurrentwidelyknown":"0","cam_scorecurrentwidelyknownexploited":"0","ipprotocol":"","cvss_accessvector":"N","cvss_accesscomplexity":"L","cvss_authentication":null,"cvss_confidentialityimpact":"C","cvss_integrityimpact":"N","cvss_availabilityimpact":"N","cvss_exploitablity":null,"cvss_remediationlevel":"OF","cvss_reportconfidence":"C","cvss_collateraldamagepotential":"ND","cvss_targetdistribution":"M","cvss_securityrequirementscr":"ND","cvss_securityrequirementsir":"ND","cvss_securityrequirementsar":"ND","cvss_basescore":"7.8","cvss_basevector":"AV:N/AC:L/Au:N/C:C/I:N/A:N","cvss_temporalscore":"6.1","cvss_environmentalscore":"4.57255757448","cvss_environmentalvector":"CDP:ND/TD:M/CR:ND/IR:ND/AR:ND","metric":0.0,"vulnote":null}