dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-10118

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
SECOM WRTR-304GN-304TW-UPSC does not properly filter user input in the specific functionality. Unauthenticated remote attackers can exploit this vulnerability to inject and execute arbitrary system commands on the device.

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

This is a command injection vulnerability in SECOM WRTR-304GN-304TW-UPSC devices. The affected functionality fails to properly sanitize user input, allowing unauthenticated remote attackers to inject and execute arbitrary OS commands on the device.

MitigationApply vendor firmware updates if available; otherwise, isolate the device behind a firewall or restrict network access to prevent unauthenticated attackers from reaching the vulnerable functionality.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 device model
    Access the device's web management interface or check the device label/console for the exact model number (WRTR-304GN or 304TW-UPSC)
    Affected if The device is a SECOM WRTR-304GN or 304TW-UPSC model
  2. Check if web management interface is network-accessible
    Attempt to access the device's web interface IP address from an external network segment using a browser or curl request
    Affected if The management web interface responds to requests from untrusted networks (no firewall or ACL blocking)
  3. Verify firmware version if accessible
    Log into the web interface and navigate to the firmware/version information page, or query the device's status endpoint if known
    Affected if The installed firmware version is older than any available patched version (contact vendor for version details)
  4. Inspect for command injection entry points
    Examine the web interface for parameters that accept user input (e.g., network settings, diagnostics, ping functions) and check if special characters (;, |, &, $) are filtered
    Affected if User-supplied input in web parameters is not sanitized and special characters allow command chaining

You are affected if you have a SECOM WRTR-304GN or 304TW-UPSC device with its management interface exposed to untrusted networks and the firmware has not been patched.

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

Apply vendor firmware updates if available; otherwise, isolate the device behind a firewall or restrict network access to prevent unauthenticated attackers from reaching the vulnerable functionality.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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