dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2020-13712

HIGH · 7.8 CVSS v3.1 Published 2024-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A command injection is possible through the user interface, allowing arbitrary command execution as the root user. oMG2000 running MGOS 3.15.1 or earlier is affected.  MG90 running MGOS 4.2.1 or earlier is affected.

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

Command injection vulnerability in the web interface of oMG2000 (MGOS ≤3.15.1) and MG90 (MGOS ≤4.2.1) devices allows unauthenticated attackers to execute arbitrary OS commands with root privileges through the UI.

MitigationUpgrade MGOS firmware to versions newer than 3.15.1 for oMG2000 and newer than 4.2.1 for MG90; if upgrades are not immediately feasible, restrict network access to the management interface via firewall or VPN.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 device model and MGOS version
    Access the device via console/SSH or check the web interface system info page to determine if the device is an oMG2000 or MG90, and note the installed MGOS firmware version number
    Affected if The device is an oMG2000 running MGOS version 3.15.1 or lower, or an MG90 running MGOS version 4.2.1 or lower
  2. Confirm web interface is enabled and accessible
    Verify that the web management interface (HTTP/HTTPS on ports 80/443 or vendor-specific ports) is enabled and reachable on the device
    Affected if The web interface is active and responds to requests
  3. Determine network exposure of management interface
    Check device network configuration and firewall settings to determine if the web interface is bound to all interfaces (0.0.0.0) or directly accessible from untrusted networks
    Affected if The web interface is exposed to networks other than a trusted management VLAN or localhost
  4. Verify no authentication is required for the vulnerable endpoint
    Attempt to access common CGI or API endpoints in the web interface without providing credentials to confirm if authentication is enforced
    Affected if Unauthenticated access to web interface endpoints is possible without login

The environment is affected if the device is an oMG2000 on MGOS ≤3.15.1 or an MG90 on MGOS ≤4.2.1 and the web interface is network-accessible without authentication filters.

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

Upgrade MGOS firmware to versions newer than 3.15.1 for oMG2000 and newer than 4.2.1 for MG90; if upgrades are not immediately feasible, restrict network access to the management interface via firewall or VPN.

Recommended fix High confidence

MGOS 3.15.2 or newer for oMG2000; MGOS 4.2.2 or newer for MG90

  1. 1. Identify the specific device model (oMG2000 or MG90) from the affected hardware
  2. 2. Check the current MGOS firmware version running on the device through the administrative interface
  3. 3. For oMG2000 devices: Upgrade the MGOS firmware to version 3.15.2 or later
  4. 4. For MG90 devices: Upgrade the MGOS firmware to version 4.2.2 or later
  5. 5. Obtain the firmware from Sierra Wireless official support channels following their standard upgrade procedure
  6. 6. Apply the firmware upgrade through the device's web interface or CLI as documented by Sierra Wireless
  7. 7. After upgrade, verify the device is functioning properly and the vulnerable interface is no longer exploitable
Caveat Review Sierra Wireless release notes for any configuration or compatibility changes between the current and new MGOS versions before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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