dbcve.org
ThingsproApplication · Moxa

CVE-2018-18394

CRITICAL · 9.8 CVSS v3.0 Published 2018-10-19
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
Sensitive Information Stored in Clear Text in Moxa ThingsPro IIoT Gateway and Device Management Software Solutions version 2.1.

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

Sensitive information (credentials, keys, or other secrets) is stored in clear text (unencrypted) within Moxa ThingsPro IIoT Gateway and Device Management Software version 2.1. An attacker who gains access to the system storage or backups can directly read these secrets without requiring decryption.

MitigationEncrypt all sensitive data at rest using strong encryption (AES-256 or equivalent), implement a secure key management system, rotate any exposed credentials immediately, and apply any available vendor patches.

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
ThingsproApplication
Affected:= 2.1

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 ThingsPro installation and version
    Locate the Moxa ThingsPro installation directory and determine the installed version number
    Affected if Installed version is exactly 2.1
  2. Locate credential storage files
    Search configuration directories for files that store credentials, keys, or other secrets used by ThingsPro
    Affected if Credentials or secrets are stored in clear text (unencrypted) format
  3. Inspect backup archives
    Examine any system or ThingsPro application backup files for stored sensitive data
    Affected if Backup files contain clear text credentials or secrets without encryption
  4. Examine data storage locations
    Review database files, application data directories, or other storage where ThingsPro persists sensitive information
    Affected if Sensitive data is stored in unencrypted form in application storage

A system is affected if it runs ThingsPro version 2.1 and contains clear text (unencrypted) credentials, keys, or secrets in configuration files, backups, or data storage locations.

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

Encrypt all sensitive data at rest using strong encryption (AES-256 or equivalent), implement a secure key management system, rotate any exposed credentials immediately, and apply any available vendor patches.

Recommended fix Moderate confidence

ThingsPro version 2.2 (or later)

  1. Stop the ThingsPro service to prevent changes during the upgrade.
  2. Back up the entire ThingsPro configuration directory and any stored credentials (e.g., /opt/ThingsPro or the default installation path).
  3. Download the fixed release (ThingsPro version 2.2 or later) from the official Moxa website or your vendor’s support portal.
  4. Uninstall the current version 2.1 following the vendor’s removal procedure (e.g., run the uninstaller or remove the package).
  5. Install the new version 2.2 on the gateway, following the installation guide provided by Moxa.
  6. Restore the configuration from the backup after the installation completes.
  7. Start the ThingsPro service and verify that the service is running correctly.
  8. Confirm that sensitive information (e.g., passwords, API keys) is now stored in an encrypted format by inspecting the configuration files or using vendor verification tools.
Caveat Review the release notes for any configuration format changes or breaking changes that may affect existing integrations.

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

Fix this in Thingspro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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