dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-12849

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click 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
Multiple OS command injection vulnerabilities exist in the libNetSetObj.so functionality of GeoVision GV-I/O Box 4E 2.09. A specially crafted network packet can lead to command execution. An attacker can send a network request to trigger this vulnerability. `libNetSetObj.so` is an internal library used by various binaries on the device to configure the network stack (start and stop various services, configure IP, Netmask, gateway, dns, etc.) #### CNetSetObj::m_F_n_Set_Net_Mask command injection The following function takes a string as a net mask address, performs no sanitization on it and calls `system`. This is a classic command injection vulnerability. The function is reachable from both the network-exposed `DVRSearch` service and the `Network.cgi` endpoint. int __fastcall CNetSetObj::m_F_n_Set_Net_Mask(const char **this, char *netmask_addr) { bool v2; // zf char v4[72]; // [sp+0h] [bp-48h] BYREF v2 = *this == 0; if ( *this ) v2 = netmask_addr == 0; if ( v2 ) return 0; sprintf(v4, "/sbin/ifconfig %s netmask %s", *this, netmask_addr); // attacker controlled netmask_addr system(v4); return 1; }

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

OS command injection in GeoVision GV-I/O Box 4E v2.09 where the CNetSetObj::m_F_n_Set_Net_Mask function passes the attacker-controlled netmask parameter directly into a sprintf-formatted string executed via system(). The vulnerable code constructs '/sbin/ifconfig %s netmask %s' without any input sanitization, allowing arbitrary command execution. The DVRSearch service exposes this vulnerability to network attackers.

MitigationImplement strict input validation for netmask format (e.g., using inet_pton to validate IP/netmask syntax) and replace the system() call with safer alternatives such as execve() with explicit arguments. Network-exposed services should be restricted behind authentication or network segmentation until patched.

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
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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. Identify the device model
    Query the device on the network or access its admin interface to confirm it is a GeoVision GV-I/O Box 4E. This may be done via HTTP admin panel, SNMP, or by checking device information endpoints if available.
    Affected if The device is a GeoVision GV-I/O Box 4E and the firmware version is v2.09.
  2. Determine the firmware version
    Access the device admin interface or use the vendor-provided tool to check the installed firmware version. Compare the version number to v2.09.
    Affected if The installed firmware version is v2.09 (the only version explicitly mentioned as vulnerable in the summary).
  3. Verify DVRSearch service exposure
    Scan the network for open ports associated with the DVRSearch service (commonly UDP/8554 or similar, check documentation for the specific port). Use a network scanner to determine if this service is listening on accessible network interfaces.
    Affected if The DVRSearch service is exposed to an untrusted network, allowing remote attackers to reach the vulnerable function.
  4. Confirm netmask configuration is accessible
    Verify that the network settings interface, specifically the netmask configuration feature reachable through CNetSetObj::m_F_n_Set_Net_Mask, is accessible either locally or remotely.
    Affected if The netmask configuration interface can be invoked without proper authentication or network segmentation.

You are affected if you have a GeoVision GV-I/O Box 4E running firmware v2.09 with the DVRSearch service exposed to an untrusted network, allowing remote attackers to inject commands via the netmask parameter.

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 strict input validation for netmask format (e.g., using inet_pton to validate IP/netmask syntax) and replace the system() call with safer alternatives such as execve() with explicit arguments. Network-exposed services should be restricted behind authentication or network segmentation until patched.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12849 — 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-12849 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