dbcve.org
Oncell G3110 Hspa FirmwareOperating system · Moxa

CVE-2017-7913

CRITICAL · 9.8 CVSS v3.0 Published 2017-05-29
Fix available
A fix is available. Upgrade to after 1.4 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
A Plaintext Storage of a Password issue was discovered in Moxa OnCell G3110-HSPA Version 1.3 build 15082117 and previous versions, OnCell G3110-HSDPA Version 1.2 Build 09123015 and previous versions, OnCell G3150-HSDPA Version 1.4 Build 11051315 and previous versions, OnCell 5104-HSDPA, OnCell 5104-HSPA, and OnCell 5004-HSPA. The application's configuration file contains parameters that represent passwords in plaintext.

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

The Moxa OnCell series wireless cellular gateways store user credentials in plaintext within the device's configuration file. An attacker who obtains access to the configuration file (through backup extraction, file system access, or other means) can read stored passwords in cleartext, enabling unauthorized access to the device and connected systems.

MitigationImplement cryptographic hashing or encryption for passwords stored in configuration files, implement proper access controls on configuration files, and rotate all credentials that may have been exposed. Consider upgrading to patched firmware versions if available.

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
Oncell G3110 Hspa FirmwareOperating system
Affected:<= 1.3
Oncell G3110 Hsdpa FirmwareOperating system
Affected:<= 1.2
Oncell G3150 Hsdpa FirmwareOperating system
Affected:<= 1.4
Oncell 5104 Hsdpa FirmwareOperating system
Affected:<= -
Oncell 5104 Hspa FirmwareOperating system
Affected:<= -
Oncell 5004 Hspa FirmwareOperating system
Affected:<= -

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

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

  1. Identify your OnCell device model
    Access the device web interface or CLI and record the exact model number (e.g., G3110, G3150, 5104, 5004)
    Affected if The model is one of: OnCell G3110, OnCell G3150, OnCell 5104, or OnCell 5004
  2. Check the installed firmware version
    Access the device web interface under System Settings or use the CLI command to display firmware version
    Affected if For G3110 Hspa: version is 1.3 or lower. For G3110 Hsdpa: version is 1.2 or lower. For G3150 Hsdpa: version is 1.4 or lower. For 5104 or 5004 models: any version (version ranges not fully specified)
  3. Obtain the device configuration file
    Export the configuration through the device web interface (Configuration > Backup/Restore), FTP access, or device backup feature. The file is typically named config.bin, config.xml, or similar
    Affected if You have access to extract the configuration file from the device
  4. Inspect configuration file for plaintext passwords
    Open the configuration file in a text editor or use 'strings' command. Search for password fields or look for patterns matching user credentials
    Affected if Passwords appear in cleartext (readable alphanumeric strings) rather than hashed or encrypted values in the configuration file
  5. Check for user account entries
    Locate sections in the configuration file related to user accounts, admin settings, or authentication. Look for fields named 'password', 'user', 'passwd', or similar
    Affected if User account entries contain readable password strings alongside usernames

You are affected if you have a Moxa OnCell device from the affected model list running an affected firmware version AND your configuration file contains plaintext passwords rather than hashed or encrypted values.

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 1.4
Interim mitigation

Implement cryptographic hashing or encryption for passwords stored in configuration files, implement proper access controls on configuration files, and rotate all credentials that may have been exposed. Consider upgrading to patched firmware versions if available.

Fix this in Oncell G3110 Hspa Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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