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

> Authenticated super-users can execute arbitrary OS commands by editing a configuration script in Meinberg Lantime devices.

- **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:** 20 Jan 2020
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-924j-9954-rvrv

## What is CVE-2020-7240?

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

### Official description

Meinberg Lantime M300 and M1000 devices allow attackers (with privileges to configure a device) to execute arbitrary OS commands by editing the /config/netconf.cmd script (aka Extended Network Configuration). Note: According to the description, the vulnerability requires a fully authenticated super-user account using a webUI function that allows super users to edit a script supposed to execute OS commands. The given weakness enumeration (CWE-78) is not applicable in this case as it refers to abusing functions/input fields not supposed to be accepting OS commands by using 'Special Elements.

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

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

It affects 2 products.


Products: Meinbergglobal Lantime M1000 Firmware, Meinbergglobal Lantime M300 Firmware.

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

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

## Is CVE-2020-7240 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7240 is a high-severity command injection vulnerability in n/a, published on 20 Jan 2020. 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-7240 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-7240/ (Markdown: https://insights.sbomify.com/CVE-2020-7240/index.md)
```

## Sources

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

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