# CVE-2020-21992: Command injection in n/a

> Authenticated attackers can execute arbitrary system commands as root via unsanitized input in the SmartLiving web interface.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-35c4-jff8-4jgv

## What is CVE-2020-21992?

CVE-2020-21992 is a high-severity command injection vulnerability in n/a, published on 29 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Inim Electronics SmartLiving SmartLAN/G/SI <=6.x suffers from an authenticated remote command injection vulnerability. The issue exist due to the 'par' POST parameter not being sanitized when called with the 'testemail' module through web.cgi binary. The vulnerable CGI binary (ELF 32-bit LSB executable, ARM) is calling the 'sh' executable via the system() function to issue a command using the mailx service and its vulnerable string format parameter allowing for OS command injection with root privileges. An attacker can remotely execute system commands as the root user using default credentials and bypass access controls in place.

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

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

It affects 6 products.


Products: Inim Smartliving 10100l Firmware, Inim Smartliving 10100lg3 Firmware, Inim Smartliving 1050 Firmware, Inim Smartliving 1050g3 Firmware, Inim Smartliving 505 Firmware, Inim Smartliving 515 Firmware.

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

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

## Is CVE-2020-21992 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-21995](https://insights.sbomify.com/CVE-2020-21995/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-22002](https://insights.sbomify.com/CVE-2020-22002/): Server-side request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-21992 is a high-severity command injection vulnerability in n/a, published on 29 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-21992 in the wild and no public exploit code.

Affected product: n/a. 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-21992/ (Markdown: https://insights.sbomify.com/CVE-2020-21992/index.md)
```

## Sources

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

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