{"vuid":"VU#973635","idnumber":"973635","name":"Some SSH servers on Microsoft Windows set insecure permissions for the host identification key file","keywords":["ssh server","hostkey","insecure file permissions","local access error","RQ #11775"],"overview":"SSH provides remote, encrypted terminal access to hosts. Some SSH servers, when running on Microsoft Windows, set insecure permissions on the file storing the private SSH server hostkey. This could allow an authenticated user to obtain the SSH hostkey and use it to impersonate the server.","clean_desc":"Some SSH servers create the hostkey with permissions that allow any user to read the file. As a result, any user logged into the system can read the private SSH hostkey. The hostkey is used to authenticate the server to the client. This defends against redirection attacks, such as DNS hijacking that cause the client to connect to a malicious server. In such cases, clients that know the public hostkey can verify that the server has the private hostkey, thereby verifying the server is correct.","impact":"If an attacker copies the private hostkey of a server, they can configure a server with the same private key as the legitimate server. Such a server would appear valid to clients if another attack, such as DNS hijacking, was used to trick the client into connecting to the attacker's server.","resolution":"Upgrade Upgrade per vendor information. Hostkey Regeneration Regardless of how the vulnerability is addressed, the hostkey may already have been compromised. Regenerating the hostkey will address this problem, although SSH clients with the old key will emit warnings when connecting to the server after the hostkey has been regenerated.","workarounds":"Workaround Correct Permissions Manually change the permissions on the hostkey file so that only the Administrator group can read the file. The default file in which the private hostkey file is stored varies by vendor.","sysaffected":"","thanks":"Thanks to SSH Communications Security for reporting this vulnerability.","author":"This document was written by Hal Burch.","public":["http://www.ssh.com/company/newsroom/article/653/","http://www.securityfocus.com/infocus/1806","http://secunia.com/advisories/15894","http://www.securityfocus.com/bid/14116/info","http://securitytracker.com/alerts/2005/Jun/1014343.html","http://xforce.iss.net/xforce/xfdb/21217"],"cveids":["CVE-2005-2146"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2005-07-15T20:35:46Z","publicdate":"2005-06-30T00:00:00Z","datefirstpublished":"2005-07-18T19:57:44Z","dateupdated":"2005-09-09T18:48:28Z","revision":38,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"20","cam_exploitation":"0","cam_internetinfrastructure":"3","cam_population":"8","cam_impact":"5","cam_easeofexploitation":"20","cam_attackeraccessrequired":"10","cam_scorecurrent":"3.45","cam_scorecurrentwidelyknown":"3.45","cam_scorecurrentwidelyknownexploited":"6.45","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":3.45,"vulnote":null}