{"vuid":"VU#165290","idnumber":"165290","name":"WebEOC handles sensitive information in an insecure manner","keywords":["WebEOC","information disclosure","password","username","URI","HTML"],"overview":"WebEOC handles sensitive information in an insecure manor. As a result, sensitive information may be exposed to untrusted parties.","clean_desc":"WebEOC is a web-based crisis information management application that provides functions to gather, coordinate, and disseminate information between emergency personnel and Emergency Operations Centers (EOC). By design, WebEOC insecurely stores sensitive information in easily accessible application components. Sensitive information includes, but is not necessarily limited to: System configuration information\nUsernames\nPasswords\nEmergency information\nMedical/victim information In numerous places throughout the WebEOC application this type of information is handled in an insecure manor. Sensitive information may be encoded into URIs, stored in publicly accessible configuration files, and stored with HTML code that is presented to users. In addition, sensitive information that is exposed to users is often plaintext. Attackers and untrusted users can easily access sensitive information","impact":"Sensitive information may be easily accessible to untrusted parties. In some cases, this information may be stored as plaintext.","resolution":"Upgrade\nVersion 6.0.2 corrects this vulnerability. According to ESi: These vulnerabilities have been addressed in WebEOC version 6.0.2. Each of the application areas that exposed sensitive information were modified so that the sensitive information is no longer exposed. Much of this sensitive information was moved to different parts of the application and stored on the server in areas that are only accessible to authenticated/trusted users. A general policy has been implemented that reduces the amount of information that is passed between the client and the server, thus reducing the likelihood that sensitive information would be transmitted in an insecure manner. To obtain WebEOC upgrades, contact ESi Technical Support.","workarounds":"","sysaffected":"","thanks":"This document is based on technical analysis by IOActive and additional information from ESi. Thanks also to the City of Seattle for bringing this to our attention.","author":"This document was written by Jeff Gennari.","public":["http://www.esi911.com/esi/products/webeoc.shtml","http://www.esi911.com/esi/support/support.htm"],"cveids":["CVE-2005-2285"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2005-04-20T15:41:07Z","publicdate":"2005-07-13T00:00:00Z","datefirstpublished":"2005-07-13T14:59:15Z","dateupdated":"2005-07-14T16:40:11Z","revision":63,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"5","cam_exploitation":"0","cam_internetinfrastructure":"4","cam_population":"15","cam_impact":"9","cam_easeofexploitation":"20","cam_attackeraccessrequired":"10","cam_scorecurrent":"4.55625","cam_scorecurrentwidelyknown":"12.15","cam_scorecurrentwidelyknownexploited":"22.275","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":4.55625,"vulnote":null}