Description
An insufficient encryption vulnerability exists in the Device Authentication functionality of GeoVision GV-IP Device Utility 9.0.5. Listening to broadcast packets can lead to credentials leak. An attacker can listen to broadcast messages to trigger this vulnerability.
When interacting with various Geovision devices on the network, the utility may send privileged commands; in order to do so, the username and password of the device need to be provided. In some instances the command is broadcasted over UDP and the username/password are encrypted using a cryptographic protocol that appears to be derivated from Blowfish. However the symmetric key used for the encryption is also included in the packet, and thus the security of the username/password only relies on the "obscurity" of the encryption scheme. An attacker on the same LAN can listen to the broadcast traffic once an admin user interacts with the device, and decrypt the credentials using their own implementation of the algorithm. With this password the attacker would have full control over the device configuration, allowing them to change its ip address or even reset it to factory default.
When interacting with various Geovision devices on the network, the utility may send privileged commands; in order to do so, the username and password of the device need to be provided. In some instances the command is broadcasted over UDP and the username/password are encrypted using a cryptographic protocol that appears to be derivated from Blowfish. However the symmetric key used for the encryption is also included in the packet, and thus the security of the username/password only relies on the "obscurity" of the encryption scheme. An attacker on the same LAN can listen to the broadcast traffic once an admin user interacts with the device, and decrypt the credentials using their own implementation of the algorithm. With this password the attacker would have full control over the device configuration, allowing them to change its ip address or even reset it to factory default.
No analysis available yet.
Remediation
Vendor Solution
GeoVision GV-IP Device Utility Device Authentication version 9.0.7.0 has patched reported vulnerability.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
History
Mon, 27 Apr 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An insufficient encryption vulnerability exists in the Device Authentication functionality of GeoVision GV-IP Device Utility 9.0.5. Listening to broadcast packets can lead to credentials leak. An attacker can listen to broadcast messages to trigger this vulnerability. When interacting with various Geovision devices on the network, the utility may send privileged commands; in order to do so, the username and password of the device need to be provided. In some instances the command is broadcasted over UDP and the username/password are encrypted using a cryptographic protocol that appears to be derivated from Blowfish. However the symmetric key used for the encryption is also included in the packet, and thus the security of the username/password only relies on the "obscurity" of the encryption scheme. An attacker on the same LAN can listen to the broadcast traffic once an admin user interacts with the device, and decrypt the credentials using their own implementation of the algorithm. With this password the attacker would have full control over the device configuration, allowing them to change its ip address or even reset it to factory default. | |
| Title | GeoVision GV-IP Device Utility Device Authentication insufficient encryption vulnerability | |
| First Time appeared |
Geovision Inc.
Geovision Inc. gv-ip Device Utility |
|
| Weaknesses | CWE-656 | |
| CPEs | cpe:2.3:a:geovision_inc.:gv-ip_device_utility:9.0.5.0:*:windows:*:*:*:*:* | |
| Vendors & Products |
Geovision Inc.
Geovision Inc. gv-ip Device Utility |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GV
Published:
Updated: 2026-04-26T23:58:49.334Z
Reserved: 2026-04-26T23:39:08.350Z
Link: CVE-2026-42363
No data.
Status : Received
Published: 2026-04-27T00:16:20.357
Modified: 2026-04-27T00:16:20.357
Link: CVE-2026-42363
No data.
OpenCVE Enrichment
No data.
Weaknesses