CVE-2018-11422
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 · uneditedMoxa OnCell G3100-HSPA Series version 1.6 Build 17100315 and prior use a proprietary configuration protocol that does not provide confidentiality, integrity, and authenticity security controls. All information is sent in plain text, and can be intercepted and modified. Any commands (including device reboot, configuration download or upload, or firmware upgrade) are accepted and executed by the device without authentication.
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 confidenceThe Moxa OnCell G3100-HSPA Series cellular gateway uses a proprietary configuration protocol that transmits all data in cleartext without encryption, allowing attackers to intercept and modify traffic. The device also fails to authenticate any commands, permitting unauthenticated attackers to execute privileged operations including device reboot, configuration upload/download, and firmware upgrades.
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<= 1.6<= 1.6CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device model and firmware versionAccess the device web interface or console and navigate to the firmware version information page, typically found under Status or System settings. Record the exact firmware version number.Affected if The firmware version is 1.6 or lower for Moxa OnCell G3150 HSPA or G3150 HSPA T models.
-
Verify if the proprietary configuration protocol port is exposedScan the device for open ports, specifically port 4900 (the default port for Moxa's proprietary protocol). Use a network scanner or nmap command: nmap -p 4900 <device_ip>. Check if this port is accessible from untrusted networks.Affected if Port 4900 is open and accessible from any network segment that is not isolated from untrusted users.
-
Test web interface authentication enforcementAttempt to access the device web management interface without providing any credentials. Try accessing common paths like / or /home. Observe if the interface loads fully or returns an authentication prompt.Affected if The web interface loads completely or allows access to administrative functions without requiring any login credentials.
-
Test command execution without authenticationSend an HTTP request to the device attempting to trigger a privileged operation such as a reboot or configuration download, without including any session tokens or authentication headers. Example: curl http://<device_ip>/reboot or similar endpoint.Affected if The device executes the command or returns configuration data without rejecting the request due to missing authentication.
-
Check network exposure of management interfacesReview firewall rules or network ACLs to determine if the device management ports (web interface port 80/443 and proprietary protocol port 4900) are exposed to untrusted networks such as the internet or DMZ segments.Affected if Management interfaces are reachable from networks beyond the trusted internal network segment.
A user is affected if they are running firmware version 1.6 or lower on a G3150 HSPA or HSPA T device and the device or its management interfaces are accessible from any network where untrusted users could send unauthenticated requests.
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 dataImplement network segmentation to isolate the device; contact Moxa for firmware updates that address the authentication and encryption deficiencies; if no update is available, consider compensating controls such as VPN tunnels or physical access restrictions.
- Consultation6.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11422 — 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-2018-11422 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