dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-13605

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Zero-click

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
3onedata modbus gateway device model GW1101-1D(RS-485)-TB-P (hardware version V2.2.0) allows authenticated users to execute arbitrary shell commands in the context of the root user by providing payload in the "IP address" field of the diagnosis test tools. This issue has been resolved in firmware version 3.0.59B2024080600R4353

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

Authenticated command injection vulnerability in 3onedata GW1101-1D modbus gateway. The diagnosis test tool's IP address field accepts unsanitized input that gets executed as shell commands in the context of the root user, allowing full system compromise.

MitigationUpgrade firmware to version 3.0.59B2024080600R4353 or later. Until then, restrict access to authenticated diagnostic functions and monitor for unauthorized command execution.

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
Adjacent
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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
    Access the device web interface or check the device label/marketing materials to confirm it is a 3onedata GW1101-1D modbus gateway. Alternatively, check the HTTP Server header or SNMP sysDescr for 'GW1101-1D'.
    Affected if The device is a 3onedata GW1101-1D modbus gateway.
  2. Check the firmware version
    Log into the device web interface and navigate to System > Firmware Version or System > Status to view the installed firmware version. Compare it to the fixed version 3.0.59B2024080600R4353.
    Affected if The firmware version is lower than 3.0.59B2024080600R4353.
  3. Locate the diagnosis test tool
    In the device web interface, navigate to Diagnostics or Diagnosis Test tool. Look for a feature that tests network connectivity or allows entering an IP address for testing purposes.
    Affected if The diagnosis test tool with an IP address input field is present and accessible.
  4. Verify if authentication is required
    Check if the diagnosis test tool is accessible only after logging in with valid credentials. Attempt to access the diagnostic function without authentication to confirm an authenticated attacker is required.
    Affected if The vulnerability requires authenticated access, so the diagnostic tool is behind a login.
  5. Check for unauthorized command execution
    Review system logs (usually in System > Logs or /var/log/) for suspicious commands, unexpected shell invocations, or connections from the diagnostic function. Look for abnormal processes or newly created files indicating command injection.
    Affected if Unexpected shell commands, suspicious processes, or unauthorized configuration changes are found in logs or on the filesystem.

A user is affected if they have a 3onedata GW1101-1D device running firmware older than version 3.0.59B2024080600R4353 with the diagnosis test tool accessible to authenticated users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade firmware to version 3.0.59B2024080600R4353 or later. Until then, restrict access to authenticated diagnostic functions and monitor for unauthorized command execution.

Recommended fix High confidence

3.0.59B2024080600R4353

  1. Obtain the firmware version 3.0.59B2024080600R4353 from the official 3onedata website or support channels
  2. Log in to the GW1101-1D(RS-485)-TB-P device web interface with administrator credentials
  3. Navigate to the firmware upgrade or system settings section in the web management interface
  4. Upload the firmware file version 3.0.59B2024080600R4353
  5. Wait for the firmware upload and installation to complete - do not power off the device during this process
  6. After the device reboots, verify the firmware version has been updated to 3.0.59B2024080600R4353 in the device status or about section
  7. Log in and verify the diagnosis test tools now properly sanitize input in the IP address field

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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