dbcve.org
Uc 2101 Lx FirmwareOperating system · Moxa

CVE-2022-3088

HIGH · 7.8 CVSS v3.1 Published 2022-11-28
Fix available
A fix is available. Upgrade to after 1.12 or later.
See remediation →
80/100
Remediation priority · High
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
UC-8100A-ME-T System Image: Versions v1.0 to v1.6, UC-2100 System Image: Versions v1.0 to v1.12, UC-2100-W System Image: Versions v1.0 to v 1.12, UC-3100 System Image: Versions v1.0 to v1.6, UC-5100 System Image: Versions v1.0 to v1.4, UC-8100 System Image: Versions v3.0 to v3.5, UC-8100-ME-T System Image: Versions v3.0 and v3.1, UC-8200 System Image: v1.0 to v1.5, AIG-300 System Image: v1.0 to v1.4, UC-8410A with Debian 9 System Image: Versions v4.0.2 and v4.1.2, UC-8580 with Debian 9 System Image: Versions v2.0 and v2.1, UC-8540 with Debian 9 System Image: Versions v2.0 and v2.1, and DA-662C-16-LX (GLB) System Image: Versions v1.0.2 to v1.1.2 of Moxa's ARM-based computers have an execution with unnecessary privileges vulnerability, which could allow an attacker with user-level privileges to gain root privileges.

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 · moderate confidence

Multiple Moxa ARM-based computer systems (UC-8100A-ME-T, UC-2100, UC-2100-W, UC-3100, UC-5100, UC-8100, UC-8200, AIG-300, UC-8410A, UC-8580, UC-8540, DA-662C-16-LX) contain a privilege escalation vulnerability where an attacker with user-level privileges can gain root privileges through execution with unnecessary privileges.

MitigationApply vendor-provided firmware updates to affected devices to patch the privilege escalation vulnerability. Until patches are available, minimize user access and monitor for suspicious privilege escalation attempts.

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
Uc 2101 Lx FirmwareOperating system
Affected:>= 1.0, <= 1.12
Uc 2102 Lx FirmwareOperating system
Affected:>= 1.0, <= 1.2
Uc 2104 Lx FirmwareOperating system
Affected:>= 1.0, <= 1.2
Uc 2111 Lx FirmwareOperating system
Affected:>= 1.0, <= 1.2
Uc 2112 Lx FirmwareOperating system
Affected:>= 1.0, <= 1.2
Uc 2102 T Lx FirmwareOperating system
Affected:>= 1.0, <= 1.2
Uc 2114 T Lx FirmwareOperating system
Affected:>= 1.0, <= 1.2
Uc 2116 T Lx FirmwareOperating system
Affected:>= 1.0, <= 1.2

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 the Moxa device model
    Access the device console, web interface, or check the device label to confirm the exact model number (e.g., UC-2101-LX, UC-2102-LX, UC-2111-LX, etc.)
    Affected if The device model matches one of the affected models listed in the CVE (UC-2100 series, UC-5100, UC-8100 series, AIG-300, UC-8410A, UC-8580, UC-8540, DA-662C-16-LX)
  2. Determine the firmware version
    Log into the device via SSH or console and run the command to check firmware version, typically 'show version' or check through the web interface under System > Information
    Affected if The installed firmware version falls within the affected ranges: UC-2101-LX version 1.0 to 1.12, UC-2102-LX version 1.0 to 1.2, UC-2104-LX version 1.0 to 1.2, UC-2111-LX version 1.0 to 1.2, UC-2112-LX version 1.0 to 1.2, UC-2102T-LX version 1.0 to 1.2, UC-2114T-LX version 1.0 to 1.2, or UC-2116T-LX
  3. Verify presence of non-root user accounts
    Check for existing user accounts on the device by examining /etc/passwd or using 'cat /etc/shadow' (if accessible) or listing users via the web interface under User Management
    Affected if Non-root user accounts exist on the device, providing an attack vector for privilege escalation
  4. Check for unusual process execution with elevated privileges
    Review system logs and running processes for any user-level processes executing with root or elevated privileges, using commands like 'ps aux' or reviewing /var/log/messages
    Affected if User-level processes are observed running with root-level privileges, indicating the vulnerability may be exploited

The environment is affected if the device is a Moxa ARM-based system (particularly UC-2100 series variants) running firmware within the listed version ranges and non-root user accounts have access to the device.

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.12
Interim mitigation

Apply vendor-provided firmware updates to affected devices to patch the privilege escalation vulnerability. Until patches are available, minimize user access and monitor for suspicious privilege escalation attempts.

Fix this in Uc 2101 Lx Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation10.0 h
  • Testing8.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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