dbcve.org
Oncellg3470a Lte FirmwareOperating system · Moxa

CVE-2016-8363

CRITICAL · 10.0 CVSS v3.0 Published 2017-02-13
Fix available
A fix is available. Upgrade to after 10-31-2016 or later.
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
An issue was discovered in Moxa OnCell OnCellG3470A-LTE, AWK-1131A/3131A/4131A Series, AWK-3191 Series, AWK-5232/6232 Series, AWK-1121/1127 Series, WAC-1001 V2 Series, WAC-2004 Series, AWK-3121-M12-RTG Series, AWK-3131-M12-RCC Series, AWK-5232-M12-RCC Series, TAP-6226 Series, AWK-3121/4121 Series, AWK-3131/4131 Series, and AWK-5222/6222 Series. User is able to execute arbitrary OS commands on the server.

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 an OS command injection vulnerability in Moxa industrial wireless devices (OnCell and AWK series). An attacker can execute arbitrary operating system commands on the device, likely through unsanitized input in a web management interface parameter. The CVSS 10 score indicates trivial exploitability with no authentication required and complete system compromise potential.

MitigationApply vendor patches if available; if patches unavailable, restrict management interface access via firewall rules, disable remote management, or replace end-of-life devices. Implement network segmentation to isolate industrial wireless devices.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Oncellg3470a Lte FirmwareOperating system
Affected:<= 10-31-2016
Awk 4131a FirmwareOperating system
Affected:<= 10-31-2016
Awk 3191 FirmwareOperating system
Affected:<= 05-30-2017
Awk 5232 FirmwareOperating system
Affected:<= 05-30-2017
Awk 6232 FirmwareOperating system
Affected:<= 05-30-2017
Awk 1121 FirmwareOperating system
Affected:<= 06-29-2017
Awk 1127 FirmwareOperating system
Affected:<= 06-29-2017
Wac 1001 V2 FirmwareOperating system
Affected:<= 06-29-2017

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.0/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 checks

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

  1. Identify the Moxa device model
    Access the device web management interface and locate the device information page, or use the device's console to run 'show system info' or similar command to display the model number
    Affected if The device is an OnCell G3470A LTE, AWK 4131A, AWK 3191, AWK 5232, AWK 6232, AWK 1121, AWK 1127, or WAC 1001 V2 model
  2. Determine the firmware version
    In the web interface, navigate to System Settings or Status page to view firmware version; alternatively, access CLI and run 'show version' or '固件版本' command
    Affected if The installed firmware version date is on or before the cutoff date for your model (OnCell/AWK 4131A: 10-31-2016; AWK 3191/5232/6232: 05-30-2017; AWK 1121/1127/WAC 1001 V2: 06-29-2017)
  3. Verify web management interface is enabled
    Check the device network configuration via web UI under Network Settings or via CLI command 'show ip interface' to see if HTTP/HTTPS management is permitted
    Affected if The web management interface (HTTP port 80 or HTTPS port 443) is accessible and enabled on the device
  4. Confirm device is exposed to network
    Review firewall rules or access control lists that protect the device; check if the management interface IP is reachable from untrusted networks
    Affected if The device web management interface is reachable from outside the local management network or from the internet

A user is affected if they have a vulnerable OnCell or AWK series device with firmware dated on or before the cutoff for that model, and the web management interface is accessible on the network.

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
Upgrade available Upgrade to a release after 10-31-2016
Interim mitigation

Apply vendor patches if available; if patches unavailable, restrict management interface access via firewall rules, disable remote management, or replace end-of-life devices. Implement network segmentation to isolate industrial wireless devices.

Fix this in Oncellg3470a Lte Firmware 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 the upgrade done

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-2016-8363 — 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-2016-8363 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