{"vuid":"VU#258834","idnumber":"258834","name":"WebEOC privileges are based on client-side authorization","keywords":["WebEOC","Client-side authorization","elevated privileges"],"overview":"WebEOC ties privileges and roles to client-side resources. If an attacker can access a resource directly, that attacker will be granted all the privileges associated with that resource.","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). WebEOC privileges and authorizations are granted to a user based on the resources they are accessing. It is assumed that if a user can navigate to a specific resource, then that user is authorized to use that resource and obtain all privileges associated with it. In numerous places in a WebEOC system, resources are requested via URIs. An attacker may be able exploit this design by crafting a URI that will directly access a resource, thus elevating that attacker's privileges.","impact":"Attackers may be able to gain elevated privileges giving them access to sensitive information and resources.","resolution":"Upgrade\nVersion 6.0.2 corrects this vulnerability. According to ESi: In version 6.0.2 this vulnerability has been addressed by adding validation checks to all function calls submitted to the web server. Any resource request sent to the WebEOC application is validated at the server to ensure that the user is logged in and has the proper permissions. 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","http://secunia.com/advisories/16075/"],"cveids":["CVE-2005-2286"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2005-04-20T15:58:30Z","publicdate":"2005-07-13T00:00:00Z","datefirstpublished":"2005-07-13T14:58:57Z","dateupdated":"2005-07-20T03:58:49Z","revision":71,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"5","cam_exploitation":"0","cam_internetinfrastructure":"4","cam_population":"15","cam_impact":"18","cam_easeofexploitation":"15","cam_attackeraccessrequired":"10","cam_scorecurrent":"6.834375","cam_scorecurrentwidelyknown":"18.225","cam_scorecurrentwidelyknownexploited":"33.4125","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":6.834375,"vulnote":null}