{"vuid":"VU#609840","idnumber":"609840","name":"RSA Security ACE/Agent for Windows, ACE/Agent for Windows NT, and ACE/Agent for Windows 2000 do not properly handle null characters in URL","keywords":["RSA","WebAgent","RSA Security ACE/Agent for Windows","RSA Security ACE/Agent for Windows 2000","SecureID","%00","null","debug mode","sdiis.dll"],"overview":"RSA Security ACE/Agent for Windows, ACE/Agent for Windows NT, and ACE/Agent for Windows 2000 contain a vulnerability in which the ACE/Agent does not properly handle null characters contained in a URL. A specially crafted request may cause ACE/Agent to enter a debugging mode, possibly disclosing sensitive configuration information about the server.","clean_desc":"ProCheckup Ltd has reported a vulnerability in RSA Security ACE/Agent for Windows, ACE/Agent for Windows NT, and ACE/Agent for Windows 2000. The Windows versions of ACE/Agent can be used to protect resources on Microsoft Internet Information Server (IIS) web servers. Requests for protected resources are passed from the web server to the ACE/Agent, which is implemented in the file sdiis.dll. The ACE/Agent authenticates the request against an RSA Security ACE/Server using RSA Security SecurID technology. While processing a crafted URL containing an encoded null character, ACE/Agent may crash and return debugging information, which may be useful to an attacker. RSA Security addressed this issue in July 2001. The following ACE/Agents are not affected: RSA ACE/Agent 4.4.3 (or later) for Windows NT\nRSA ACE/Agent 1.1.2 (or later) for Windows 2000\nRSA ACE/Agent 5.0 for Windows","impact":"An attacker may be able to cause ACE/Agent to crash, possibly revealing sensitive configuration information about the server.","resolution":"This vulnerability is fixed in the versions of ACE/Agents specified in the Vendor Statement. RSA Security recommends that customers install the latest releases, which are available through RSA Security's SecurCare Online and through RSA Security's public web site. RSA Security informed customers of this vulnerability in a Security Bulletin dated July 24, 2001.","workarounds":"IIIb. Workarounds It may be possible to use an application layer filter to detect and block malicious requests.","sysaffected":"","thanks":"The CERT Coordination Center thanks \nProCheckup Ltd for information used in this document.","author":"This document was written by Art Manion.","public":["http://www.procheckup.com/vuln.html","http://www.securityfocus.com/bid/3462"],"cveids":[""],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2001-08-08T20:09:15Z","publicdate":"2001-10-19T00:00:00Z","datefirstpublished":"2001-10-19T20:08:11Z","dateupdated":"2001-11-01T19:19:57Z","revision":27,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"7","cam_exploitation":"0","cam_internetinfrastructure":"4","cam_population":"6","cam_impact":"4","cam_easeofexploitation":"20","cam_attackeraccessrequired":"20","cam_scorecurrent":"1.98","cam_scorecurrentwidelyknown":"4.32","cam_scorecurrentwidelyknownexploited":"7.92","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":1.98,"vulnote":null}