Vulnerability Note VU#170394
WebEOC account lock-out policy may allow a denial-of-service
WebEOC account lock out policy may allow a remote attacker to disable user and system accounts resulting in a denial-of-service condition.
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 implements a system-wide lock-out policy that is disables an account upon three consecutive failed login attempts. In numerous places throughout the system, an attacker can easily retrieve the information necessary (i.e. usernames) to attempt a login for a particular account. Please note that an account can represent an individual user on one WebEOC site or a system account for another WebEOC site.
Users are authenticated into the WebEOC system by entering a username and password on the WebEOC login web page. The WebEOC login webpage displays all registered usernames within a drop-down list. If a remote attacker gains access to the WebEOC login page, they can intentionally enter a wrong password three consecutive times for a particular user, locking that users account.
An unauthenticated, remote attacker may be able to exploit the lock-out policy to lock valid accounts. As a result individual users or WebEOC sites may experience a complete denial-of-service. Recoving from this attack requires a WebEOC administrator to manually unlock the attacked account.
Version 6.0.2 corrects this vulnerability. According to ESi:
Systems Affected (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|ESi||Affected||-||21 Jun 2005|
CVSS Metrics (Learn More)
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.
This document was written by Jeff Gennari.
- CVE IDs: Unknown
- Date Public: 13 Jul 2005
- Date First Published: 13 Jul 2005
- Date Last Updated: 14 Jul 2005
- Severity Metric: 1.82
- Document Revision: 127
If you have feedback, comments, or additional information about this vulnerability, please send us email.