# CVE-2020-7350: Metasploit Framework Plugin Libnotify Command Injection

> An attacker can execute arbitrary commands on the operator's terminal by providing a malicious hostname or service name via a file imported using db_import.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Apr 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cvfg-6mg6-247m

## What is CVE-2020-7350?

CVE-2020-7350 is a medium-severity command injection vulnerability in Rapid7 Metasploit Framework, published on 22 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Rapid7 Metasploit Framework versions before 5.0.85 suffers from an instance of CWE-78: OS Command Injection, wherein the libnotify plugin accepts untrusted user-supplied data via a remote computer's hostname or service name. An attacker can create a specially-crafted hostname or service name to be imported by Metasploit from a variety of sources and trigger a command injection on the operator's terminal. Note, only the Metasploit Framework and products that expose the plugin system is susceptible to this issue -- notably, this does not include Rapid7 Metasploit Pro. Also note, this vulnerability cannot be triggered through a normal scan operation -- the attacker would have to supply a file that is processed with the db_import command.

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

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

It affects 1 product.


Products: Rapid7 Metasploit.

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

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

## Is CVE-2020-7350 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-7350 exists.

Public exploit code:

- Metasploit Libnotify Plugin Arbitrary Command Execution (metasploit)

## Other vulnerabilities in Rapid7 Metasploit Framework

- [CVE-2020-7385](https://insights.sbomify.com/CVE-2020-7385/): Metasploit Framework 'drb_remote_codeexec' code execution (high 8.1)
- [CVE-2020-7377](https://insights.sbomify.com/CVE-2020-7377/): Rapid7 Metasploit Framework Relative Path Traversal in telpho10_credential_dump module (high 8.1)
- [CVE-2017-5235](https://insights.sbomify.com/CVE-2017-5235/): Other in Metasploit Pro (high 7.8)
- [CVE-2019-5645](https://insights.sbomify.com/CVE-2019-5645/): Rapid7 Metasploit HTTP Handler Denial of Service (high 7.5)
- [CVE-2019-5624](https://insights.sbomify.com/CVE-2019-5624/): Rapid7 Metasploit Framework Zip Import Directory Traversal (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7350 is a medium-severity command injection vulnerability in Rapid7 Metasploit Framework, published on 22 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-7350 exists.

Affected product: Rapid7 Metasploit Framework. 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-7350/ (Markdown: https://insights.sbomify.com/CVE-2020-7350/index.md)
```

## Sources

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

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