# CVE-2020-7697: Command Injection

> A malicious user can inject commands via the _data variable in mock2easy, leading to arbitrary code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-g4xj-wcq6-qwx5

## What is CVE-2020-7697?

CVE-2020-7697 is a critical command injection vulnerability in mock2easy, published on 29 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects all versions of package mock2easy. a malicious user could inject commands through the _data variable: Affected Area require('../server/getJsonByCurl')(mock2easy, function (error, stdout) { if (error) { return res.json(500, error); } res.json(JSON.parse(stdout)); }, '', _data.interfaceUrl, query, _data.cookie,_data.interfaceType);

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

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

2 open source packages ship an affected version, including mock2easy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mock2easy` | npm | All versions to 0.0.24 | None |
| `mock2easy` | npm | All versions to 0.0.24 | None |

Products: Mock2easy Project Mock2easy.

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

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

## Is CVE-2020-7697 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7697 is a critical command injection vulnerability in mock2easy, published on 29 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7697 in the wild and no public exploit code.

Affected packages and fixed versions:
- mock2easy (npm): affected all versions up to 0.0.24; no fix listed
- mock2easy (npm): affected all versions up to 0.0.24; no fix listed

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-7697/ (Markdown: https://insights.sbomify.com/CVE-2020-7697/index.md)
```

## Sources

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

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