CVE-2026-12485
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 · uneditedGV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and RS-485. DVRSearch is a service running by default on the IOBox listening for UDP messages on port 10001. Any user on the network can send messages to this service and interact with it. Upon receiving a UDP message, the server reads at most 1460 bytes into a local buffer and a pointer to the buffer is stored in a global variable: #### IP field stack overflow The following code is vulnerable to a stack overflow that is attacker-controlled: v3 = strlen(g_network_config->ip_addr); memcpy(&reply_buf[36], g_network_config->ip_addr, v3);
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 confidenceStack-based buffer overflow in GV-I/O Box 4E's DVRSearch service (UDP port 10001). The service copies a user-controlled IP address into a fixed 1460-byte buffer at offset 36 using memcpy without bounds checking, allowing remote attackers to overflow the stack with attacker-controlled data.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is GV-I-O Box 4EAccess the device management interface or check system information to identify the hardware model. Look for GV-I-O Box 4E in device specifications or firmware identification.Affected if The device is not a GV-I-O Box 4E - the vulnerability is specific to this model.
-
Identify if DVRSearch service is runningCheck running processes or services on the device. On Linux-based embedded systems, this may be done via 'ps' command or by checking /proc directory. Look for a process named 'DVRSearch' or a similar service binary.Affected if DVRSearch service is not present or not running - the vulnerable code path is not active.
-
Verify DVRSearch UDP service is enabledCheck network listening ports on the device. Use 'netstat -uan' or 'ss -uan' to list UDP ports. Look for DVRSearch typically bound to UDP port 4550 or similar DVR discovery ports.Affected if No UDP service for DVRSearch is listening - the attack surface is not exposed.
-
Inspect ip_addr network configurationAccess the network configuration settings for the DVRSearch service. This is typically found in the device web interface under Network Settings, or in configuration files in /etc or /var directories. Examine the ip_addr field.Affected if The ip_addr field contains a value longer than the buffer allows (exceeding typical IP address length of 15 characters plus null terminator) and DVRSearch copies this to the reply buffer at offset 36.
The environment is affected if running GV-I-O Box 4E with DVRSearch service enabled and the ip_addr field in network configuration is accessible to an attacker who can trigger the vulnerable memcpy operation.
Generated from the published advisory. Verify against your own configuration.
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 dataIsolate the device behind a firewall to block unauthorized UDP traffic to port 10001; contact vendor for patched firmware that implements proper length validation before the memcpy operation.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12485 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12485 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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