{"vuid":"VU#956762","idnumber":"956762","name":"WebEOC is vulnerable to a denial-of-service condition via uploading large files","keywords":["WebEOC","denial-of-service","DoS","uploading files","database"],"overview":"WebEOC does not properly impose size limits on files that a user can upload. This may allow a authorized attacker to exhaust system resources leading to a denial-of-service condition.","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 does not restrict the size of files that an authenticated user can upload into a back-end database. Uploading very large files may exhaust system and database resources eventually interrupting the system operations.","impact":"An authorized attacker may be able to consume a large amount of system resources. As system resources are exhausted, system operation may be disrupted resulting in a denial-of-service condition.","resolution":"Upgrade \nVersion 6.0.2 corrects this vulnerability. According to ESi: This vulnerability has been addressed in version 6.0.2 for ASP pages using the file saving mechanism in WebEOC. The file upload mechanism now checks the file size before storing the file data in the database as a binary object, limiting the total amount of data that may be uploaded into WebEOC. In an upcoming version of WebEOC this mitigation technique will be expanded to include other potential vulnerabilities. To obtain WebEOC upgrades, contact ESi Technical Support.","workarounds":"Restrict Access Restrict access to the WebEOC system to only known and trusted users.","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-2283"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2005-04-20T15:59:52Z","publicdate":"2005-07-13T00:00:00Z","datefirstpublished":"2005-07-13T15:01:54Z","dateupdated":"2005-07-20T03:32:05Z","revision":66,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"5","cam_exploitation":"0","cam_internetinfrastructure":"4","cam_population":"15","cam_impact":"3","cam_easeofexploitation":"9","cam_attackeraccessrequired":"10","cam_scorecurrent":"0.6834375","cam_scorecurrentwidelyknown":"1.8225","cam_scorecurrentwidelyknownexploited":"3.34125","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":0.6834375,"vulnote":null}