OpenVAS Manager 3.0 before 3.0.7 and 4.0 before 4.0.4 allows remote attackers to bypass the OMP authentication restrictions and execute OMP commands via a crafted OMP request for version information, which causes the state to be set to CLIENT_AUTHENTIC, as demonstrated by the omp_xml_handle_end_element function in omp.c.
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Openvas_manager | Openvas | 4.0-beta1 (including) | 4.0-beta1 (including) |
| Openvas_manager | Openvas | 4.0-beta2 (including) | 4.0-beta2 (including) |
| Openvas_manager | Openvas | 4.0-beta3 (including) | 4.0-beta3 (including) |
| Openvas_manager | Openvas | 4.0-beta4 (including) | 4.0-beta4 (including) |
| Openvas_manager | Openvas | 4.0-beta5 (including) | 4.0-beta5 (including) |
| Openvas_manager | Openvas | 4.0-rc1 (including) | 4.0-rc1 (including) |
| Openvas_manager | Openvas | 4.0.0 (including) | 4.0.0 (including) |
| Openvas_manager | Openvas | 4.0.1 (including) | 4.0.1 (including) |
| Openvas_manager | Openvas | 4.0.2 (including) | 4.0.2 (including) |
| Openvas_manager | Openvas | 4.0.3 (including) | 4.0.3 (including) |