# CVE-2020-13712: MGOS Command Injection

> Attackers can execute arbitrary commands as root via the user interface in Sierra Wireless MGOS devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2024
- **Updated:** 26 Dec 2024
- **Also known as:** GHSA-8g3g-85w5-qrm6

## What is CVE-2020-13712?

CVE-2020-13712 is a high-severity command injection vulnerability in Sierra Wireless MGOS, published on 20 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2020-13712?


## How do I fix CVE-2020-13712?

No fix has been published for CVE-2020-13712 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-13712 being exploited?

There is no known exploitation of CVE-2020-13712 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13712 and fix it if it is affected.

What it is: CVE-2020-13712 is a high-severity command injection vulnerability in Sierra Wireless MGOS, published on 20 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-13712 in the wild and no public exploit code.

Affected product: Sierra Wireless MGOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-13712/ (Markdown: https://insights.sbomify.com/CVE-2020-13712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13712
- OSV: https://osv.dev/vulnerability/CVE-2020-13712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-13712/
Summaries are generated and may contain mistakes; the official description above is the record.