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.
Security readout for executives and security teams
Plain-English summary
GeoVision’s GV-IP Device Utility can expose camera or device administrator credentials on a local network. When an administrator uses the utility, credentials may be sent in UDP broadcast traffic with encryption that is ineffective because the key is included in the packet. Anyone on the same LAN who can observe that traffic could recover credentials and control the device.
Executive priority
Treat as urgent for environments using affected GeoVision tooling. The business risk is loss of device control from local credential exposure, especially in sites where cameras or security devices share networks with broader user populations.
Technical view
CVE-2026-7161 affects GeoVision GV-IP Device Utility 9.0.5.0 and 9.0.7.0. The tool encrypts device username and password values in some UDP broadcast commands, but includes the symmetric key in the same packet. The CVSS 3.1 score is 9.3, with network attack vector, low complexity, no attacker privileges, and required user interaction.
Likely exposure
Exposure is most likely where GeoVision GV-IP Device Utility versions 9.0.5.0 or 9.0.7.0 are used on shared or insufficiently trusted LAN segments to administer GeoVision devices.
Exploitation context
The source bundle does not show KEV listing or confirmed active exploitation. Exploitation requires LAN visibility and an administrator using the utility in a way that emits vulnerable broadcast traffic. The risk is credential disclosure leading to full device configuration access.
Researcher notes
The key issue is not merely weak encryption; the packet includes material needed to decrypt credentials. The CVSS vector lists integrity impact as none, but the description says recovered credentials allow configuration control. No exploit code, patch version, or active exploitation evidence is provided in the source bundle.
Mitigation direction
Check GeoVision’s advisory for fixed versions or official mitigation guidance.
Stop using affected utility versions on shared or untrusted LANs.
Restrict administration to trusted management networks only.
Rotate GeoVision device credentials after possible LAN exposure.
Monitor devices for unexpected IP, configuration, or factory reset changes.
Validation and detection
Inventory endpoints for GV-IP Device Utility 9.0.5.0 and 9.0.7.0.
Identify networks where the utility is used for device administration.
Confirm whether untrusted hosts share those broadcast domains.
Review monitoring for GeoVision UDP broadcast traffic during administration.
Check device audit records for unauthorized configuration changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-656: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
4Timeline events
2ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-656 · source CWE mapping
Reliance on Security Through Obscurity
Reliance on Security Through Obscurity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.