{"answers":{"affected":"2 open source packages ship an affected version, including smartctl. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21810 exists.","fix":"No fix has been published for CVE-2022-21810 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21810 is a high-severity command injection vulnerability in smartctl, published on 25 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-21810 and fix it if it is affected.\n\nWhat it is: CVE-2022-21810 is a high-severity command injection vulnerability in smartctl, published on 25 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21810 exists.\n\nAffected packages and fixed versions:\n- smartctl (npm): affected all versions up to 1.0.0; no fix listed\n- smartctl (npm): affected all versions up to 1.0.0; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-21810/ (Markdown: https://insights.sbomify.com/CVE-2022-21810/index.md)","id":"CVE-2022-21810","markdown":"https://insights.sbomify.com/CVE-2022-21810/index.md","name":"CVE-2022-21810","record":{"aliases":["GHSA-69f2-4375-qv9h"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"smartctl npm package","requires_auth":"none","summary":"Attackers can execute arbitrary commands via the info method in the smartctl npm package due to improper input sanitization.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"smartctl","vendor":"smartctl_project"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"},{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"All versions of the package smartctl are vulnerable to Command Injection via the info method due to improper input sanitization.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Command injection in smartctl","id":"CVE-2022-21810","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Privilege escalation in Intel(R) HAXM software","id":"CVE-2022-21812"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"smartctl","purl":null,"source":"GHSA-69f2-4375-qv9h"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"smartctl","purl":"pkg:npm/smartctl","source":"GHSA-69f2-4375-qv9h"}],"prev":{"headline":"File upload in InRouter302","id":"CVE-2022-21809"},"products":["smartctl"],"published":"2023-01-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-01","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via the info method in the smartctl npm package due to improper input sanitization.","url":"https://insights.sbomify.com/CVE-2022-21810/"}