A vulnerability in the reclaim host role feature of Cisco Webex Meetings and Cisco Webex Meetings Server could allow an authenticated, remote attacker to take over the host role during a meeting. This vulnerability is due to a lack of protection against brute forcing of the host key. An attacker could exploit this vulnerability by sending crafted requests to a vulnerable Cisco Webex Meetings or Webex Meetings Server site. A successful exploit would require the attacker to have access to join a Webex meeting, including applicable meeting join links and passwords. A successful exploit could allow the attacker to acquire or take over the host role for a meeting.
The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Webex_meetings | Cisco | * | 40.12.0 (excluding) |
| Webex_meetings_server | Cisco | * | 3.0 (excluding) |
| Webex_meetings_server | Cisco | 3.0 (including) | 3.0 (including) |
| Webex_meetings_server | Cisco | 3.0-maintenance_release1 (including) | 3.0-maintenance_release1 (including) |
| Webex_meetings_server | Cisco | 3.0-maintenance_release2 (including) | 3.0-maintenance_release2 (including) |
| Webex_meetings_server | Cisco | 3.0-maintenance_release3 (including) | 3.0-maintenance_release3 (including) |
| Webex_meetings_server | Cisco | 3.0-maintenance_release4 (including) | 3.0-maintenance_release4 (including) |
| Webex_meetings_server | Cisco | 4.0 (including) | 4.0 (including) |
| Webex_meetings_server | Cisco | 4.0-maintenance_release1 (including) | 4.0-maintenance_release1 (including) |
| Webex_meetings_server | Cisco | 4.0-maintenance_release2 (including) | 4.0-maintenance_release2 (including) |
| Webex_meetings_server | Cisco | 4.0-maintenance_release3 (including) | 4.0-maintenance_release3 (including) |
Common protection mechanisms include:
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator. [REF-45]