dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2026-57274

HIGH · 8.3 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 password field (no key present)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer overflow vulnerability exists in GeoWebPlayer's websocket server handler for the connectionInfo command. The handle_connection_info function copies attacker-controlled JSON strings into fixed-size buffers using manual byte-by-byte loops that do not enforce length limits, allowing unbounded memory writes.

MitigationImplement proper bounds checking in all string copy operations within handle_connection_info, replace manual byte-by-byte loops with safe string functions (e.g., strncpy, snprintf) that enforce length limits, and validate input JSON string lengths before copying.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate GeoWebPlayer installation
    Search for GeoWebPlayer executables or installation directories on the system. Common paths may include /opt/, /usr/local/, or Program Files on Windows. Check running processes for geowebplayer or similar process names.
    Affected if GeoWebPlayer software is found installed on the system
  2. Identify GeoWebPlayer version
    Check the installed version by running geowebplayer --version, examining the binary metadata, or reviewing version files in the installation directory. Compare the version against any known affected version ranges.
    Affected if The installed version falls within the vulnerable version range for this CVE
  3. Verify websocket server is enabled
    Examine GeoWebPlayer configuration files (typically .conf, .json, or .xml files in the installation directory or /etc/geowebplayer/) for websocket server settings. Look for parameters like 'websocket', 'server', or 'enable' that activate the websocket handler.
    Affected if Websocket server functionality is enabled in the configuration
  4. Check connectionInfo handler status
    Inspect the websocket server configuration or handler mappings to determine if the connectionInfo command endpoint is exposed. This may be in a config file under a 'commands' or 'handlers' section.
    Affected if The connectionInfo command handler is exposed and accessible via the websocket server
  5. Inspect handle_connection_info function
    If binary analysis is possible, examine the compiled binary for the handle_connection_info function and verify whether it uses manual byte-by-byte copy loops without bounds checking. This requires reverse engineering tools or source code review if available.
    Affected if The handle_connection_info function uses vulnerable unbounded copy operations

A system is affected if GeoWebPlayer with a vulnerable version is installed with the websocket server and connectionInfo handler enabled, exposing the unbounded memory write vulnerability in handle_connection_info.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper bounds checking in all string copy operations within handle_connection_info, replace manual byte-by-byte loops with safe string functions (e.g., strncpy, snprintf) that enforce length limits, and validate input JSON string lengths before copying.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57274 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57274 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data