CVE-2026-57278: GeoWebPlayer Buffer Overflow Remote Code Execution
GeoWebPlayer, a browser plugin component shipped with GeoVision surveillance software (GV-VMS, GV-Cloud, and related products), contains a memory safety flaw in its local WebSocket server. The plugin processes JSON commands from the web interface, including one that retrieves camera connection details. An attacker who can control the JSON input—typically through a malicious web page or compromised local web interface—can send oversized strings that overflow fixed-size buffers in the connection handler. This overflow can lead to arbitrary code execution on the system running the GeoVision web service. The vulnerability requires network access and user interaction (clicking a link or visiting a compromised page), but once triggered, allows an unauthenticated attacker to take full control of the affected machine.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 8.3 HIGH · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-120
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-02 / 2026-07-02
NVD description (verbatim)
GeoWebPlayer (also called "Web Plugin" in the GV-VMS documentation and "WS Player" for VMS-Cloud) is an addon that can be installed with various GeoVision software (GV-VMS, GV-Cloud, ...). It creates a websocket server that expands the capabilities of the various web-interfaces provided by the GeoVision software and may be necessary for them to function properly. The Websocket server can accept various commands coming from localhost. One of them, `connectionInfo` is meant to provide the necessary details to connect to a camera. The handler associated with this command that we call`handle_connection_info` contains multiple instances of string copy that can overflow. The function `handle_connect_info` copies attacker-controlled JSON strings into fixed-size buffers using manual byte-by-byte loops that do not enforce length limits. #### Buffer Overflow in ip field
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-57278 is a classic stack or heap buffer overflow (CWE-120) in the `handle_connection_info` function of GeoWebPlayer's WebSocket server. The vulnerable code copies attacker-controlled JSON fields—particularly the `ip` field—into fixed-size buffers using manual byte-by-byte copying loops that lack length validation. The WebSocket server listens on localhost and accepts commands from the web interface; an attacker who can inject or modify JSON payloads sent to the server can exceed buffer boundaries and corrupt adjacent memory. Given the network accessibility (CVSS vector AV:N) and the complexity of exploitation (AC:H), successful attacks require some crafting but are feasible. The high integrity and confidentiality impact reflects the potential for code execution.
Business impact
Compromise of a GeoVision surveillance system through this vulnerability could result in unauthorized access to live video feeds and recorded footage, data theft, system downtime, and potential lateral movement into the broader network. For organizations relying on GeoVision for physical security monitoring, an attacker gaining control of the VMS could disable alarms, manipulate recordings, or establish persistence. The requirement for local or web-interface access narrows the attack surface in air-gapped deployments but expands it significantly if the web interface is exposed or accessible via VPN. This vulnerability should be treated as critical in any environment where surveillance integrity is a security control.
Affected systems
GeoWebPlayer is distributed as part of GeoVision software packages including GV-VMS, GV-Cloud, and related surveillance management platforms. The plugin is installed as an optional component to enable advanced web interface capabilities. Any installation of these products that includes the GeoWebPlayer addon is potentially affected. Version information and affected product versions should be verified against GeoVision's official advisory; this disclosure does not specify version ranges, so assume all versions are at risk until patched.
Exploitability
Exploitation requires an attacker to send a crafted JSON payload with an oversized `ip` field (or other vulnerable fields) to the GeoWebPlayer WebSocket server. The attack vector is network-based (AV:N), meaning it can originate from the network rather than requiring local code execution. However, the AC:H rating indicates non-trivial conditions must be met—likely the need for the attacker to influence which JSON is sent, or precise buffer layout knowledge. User interaction (UI:R) is required, suggesting social engineering or a malicious web page that triggers the vulnerable code path. The scope is changed (S:C), meaning the vulnerability can affect systems beyond the vulnerable component itself. Overall, this is exploitable by a skilled attacker but not a one-click attack.
Remediation
Apply the security patch from GeoVision as soon as it becomes available. Patches should address the buffer overflow by implementing proper bounds checking in the `handle_connection_info` function. Until patching is possible, restrict network access to the GeoVision web interface and disable GeoWebPlayer if it is not essential for operations. Run the GeoVision software with least-privilege account permissions to limit the impact of code execution. Consider isolating GeoVision systems on a dedicated VLAN with strict egress filtering to prevent lateral movement if compromise occurs.
Patch guidance
Consult GeoVision's security advisory for specific patched versions. Patches will likely increment the GeoWebPlayer version or the parent GV-VMS/GV-Cloud product version. Before applying patches to a production surveillance system, test in a lab environment to verify that camera connectivity, recording, and playback functions remain intact. Update all instances of GeoWebPlayer across your deployment, as a single unpatched system can serve as an entry point to the network. Verify patch application by checking the GeoWebPlayer version in the GeoVision software settings post-update.
Detection guidance
Monitor WebSocket connections to the GeoWebPlayer server (typically localhost:port, exact port varies by deployment). Look for unusual JSON payloads with exceptionally long strings in the `ip`, `port`, `hostname`, or related fields. Correlate WebSocket traffic with subsequent process crashes or unexpected child process spawning (signs of exploitation attempts). Review access logs for the GeoVision web interface for anomalous authentication patterns or requests originating from untrusted sources. Implement memory-error detection using tools like AddressSanitizer if you can run test instances. If exploitation is suspected, capture network traffic and memory dumps for forensic analysis.
Why prioritize this
Although not yet on the CISA KEV catalog, this vulnerability merits immediate prioritization due to its high CVSS score (8.3), potential for remote code execution, and the critical role surveillance systems play in organizational security. The buffer overflow is a well-understood attack primitive, and proof-of-concept code is likely to emerge once details are widely known. Organizations operating GeoVision deployments should treat this as a P0 if the software is accessible from the network or used in security-sensitive contexts. Even air-gapped deployments warrant urgent review, as insider threats or supply-chain compromises could introduce the malicious JSON.
Risk score, explained
The CVSS 3.1 score of 8.3 (HIGH) reflects a combination of factors: network accessibility (AV:N) lowers the barrier to attack; medium attack complexity (AC:H) indicates feasibility but not trivial execution; user interaction (UI:R) narrows the attack surface but is common in web-based exploitation; scope change (S:C) amplifies impact beyond the plugin itself; and full compromises of confidentiality, integrity, and availability (C:H, I:H, A:H) indicate severe post-exploitation consequences. This score appropriately reflects a vulnerability that is serious but not universally exploitable without effort.
Frequently asked questions
Can this vulnerability be exploited if the GeoVision system is on an internal network?
Yes. If an attacker can reach the network (via VPN, compromised endpoint, or insider access) or trick a user into visiting a malicious website that targets the system's WebSocket server, the vulnerability can be triggered. The network access vector (AV:N) does not require the attacker to be on the same subnet, only that network connectivity exists.
What should we do if we cannot patch immediately?
Immediately restrict access to the GeoVision web interface using firewall rules and network segmentation. Disable GeoWebPlayer if it is not critical for your operations. Run the GeoVision service under a restricted user account rather than Administrator/root. Monitor for signs of exploitation. Plan an expedited patch deployment for the next maintenance window.
Is this vulnerability being actively exploited?
As of the publication date, there is no evidence that this vulnerability is being exploited in the wild (it is not on the CISA KEV catalog). However, given the relative simplicity of buffer overflow exploitation and the surveillance-sector focus, exploitation is likely to occur after public disclosure. Act with urgency.
Does this affect only on-premises GeoVision deployments?
No. GeoVision Cloud (GV-Cloud) and any web-based deployments that use GeoWebPlayer are affected. If your surveillance data is hosted in the cloud or accessible remotely, the attack surface is broader. Coordinate with your GeoVision vendor or cloud provider to confirm patch timelines.
This analysis is provided for informational purposes and represents SEC.co's interpretation of publicly available information. No exploit code is provided herein. Organizations should verify all technical details, patch availability, and affected product versions directly with GeoVision before taking remediation steps. SEC.co does not guarantee the accuracy or completeness of this advisory and assumes no liability for actions taken in reliance on this information. Always test patches in a non-production environment before deployment. Source: NVD (public-domain), retrieved 2026-08-10. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2018-25426HIGHWinMTR 0.91 Denial-of-Service Buffer Overflow Vulnerability
- CVE-2018-25432HIGHArm Whois 3.11 Buffer Overflow Allows Local Code Execution
- CVE-2019-25733HIGHNetShareWatcher 1.5.8.0 SEH Buffer Overflow – Local Code Execution
- CVE-2019-25735HIGHAllPlayer 7.4 Buffer Overflow in URL Handling – Local Code Execution Risk
- CVE-2019-25736HIGHLabF nfsAxe 3.7 Buffer Overflow – Local Code Execution
- CVE-2025-26240HIGHJazzCore python-pdfkit 1.0.0 JavaScript Execution & File Exfiltration
- CVE-2026-0138HIGHAndroid LWIS Buffer Overflow Leading to Local Privilege Escalation
- CVE-2026-0146HIGHAndroid Media Codec Out-of-Bounds Write – RCE Risk