CVE-2023-6094
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 · uneditedA vulnerability has been identified in OnCell G3150A-LTE Series firmware versions v1.3 and prior. The vulnerability results from lack of protection for sensitive information during transmission. An attacker eavesdropping on the traffic between the web browser and server may obtain sensitive information. This type of attack could be executed to gather sensitive information or to facilitate a subsequent attack against the target.
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 OnCell G3150A-LTE Series firmware v1.3 and prior transmits sensitive information without proper encryption protection between the web browser and the device server. An attacker performing man-in-the-middle or network eavesdropping can intercept and read sensitive data in plaintext.
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.3CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 device model and firmware versionAccess the device web interface and check the system information page, or use the command-line interface (CLI) via telnet/SSH and run the 'show system' or 'version' command to display the firmware version. Compare against <= 1.3.Affected if The device is a Moxa OnCell G3150A-LTE and the firmware version is 1.3 or lower.
-
Check if HTTP is enabled for the web interfaceAttempt to access the device using HTTP (http://<device_ip>). If the login page loads over HTTP rather than HTTPS, the device is using unencrypted communication.Affected if The web interface is accessible over HTTP (port 80) without redirecting to HTTPS.
-
Verify HTTPS/TLS availabilityAttempt to access the device using HTTPS (https://<device_ip>) and check if a valid HTTPS connection is established. Check the device's web server configuration page for available protocols and verify TLS is enabled.Affected if HTTPS is either unavailable or TLS encryption is disabled in the web server settings.
-
Capture network traffic to confirm plaintext transmissionUse a network sniffer (such as Wireshark or tcpdump) on the client machine while logging into the device. Observe whether login credentials and session data are transmitted in plaintext over HTTP.Affected if Login credentials, session cookies, or other sensitive data are visible in plaintext in captured network traffic.
A user is affected if they have a Moxa OnCell G3150A-LTE device running firmware version 1.3 or lower with the web interface accessible over unencrypted HTTP.
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.
dbcve · scopedEnable TLS/HTTPS encryption for all web traffic to the device management interface, or upgrade to firmware v1.4 or later if available. Ensure network segmentation to reduce exposure to eavesdropping attacks.
OnCell G3150A-LTE firmware v1.4 or later (check Moxa for exact fixed release)
- 1. Visit Moxa's official support website at www.moxa.com to check for the latest firmware version for OnCell G3150A-LTE Series
- 2. Download the latest firmware version (ensure it is later than v1.3)
- 3. Review the firmware upgrade instructions provided in the Moxa product documentation
- 4. Backup the current device configuration before performing the firmware upgrade
- 5. Upload and install the new firmware following Moxa's recommended procedures
- 6. After upgrade, verify that the web interface is accessible via HTTPS and that sensitive communications are encrypted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6094 — 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-2023-6094 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