{"answers":{"affected":"2 open source packages ship an affected version, including semver-tags. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25853 exists.","fix":"No fix has been published for CVE-2022-25853 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25853 is a high-severity command injection vulnerability in semver-tags, published on 6 Feb 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-25853 and fix it if it is affected.\n\nWhat it is: CVE-2022-25853 is a high-severity command injection vulnerability in semver-tags, published on 6 Feb 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-25853 exists.\n\nAffected packages and fixed versions:\n- semver-tags (npm): affected all versions up to 0.4.10; no fix listed\n- semver-tags (npm): affected all versions up to 0.4.10; 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-25853/ (Markdown: https://insights.sbomify.com/CVE-2022-25853/index.md)","id":"CVE-2022-25853","markdown":"https://insights.sbomify.com/CVE-2022-25853/index.md","name":"CVE-2022-25853","record":{"aliases":["GHSA-8h3g-hcwp-6hxq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"npm semver-tags library","requires_auth":"none","summary":"Attackers can execute arbitrary commands via improper input sanitization in the getGitTagsRemote function of the semver-tags npm package.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"semver-tags","vendor":"semver-tags_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-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"All versions of the package semver-tags are vulnerable to Command Injection via the getGitTagsRemote function 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":"semver-tags is vulnerable to Command Injection via the getGitTagsRemote function","id":"CVE-2022-25853","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":"Cross-site Scripting (XSS)","id":"CVE-2022-25854"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.4.10"],"package":"semver-tags","purl":null,"source":"GHSA-8h3g-hcwp-6hxq"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.4.10"],"package":"semver-tags","purl":"pkg:npm/semver-tags","source":"GHSA-8h3g-hcwp-6hxq"}],"prev":{"headline":"Denial of Service (DoS)","id":"CVE-2022-25852"},"products":["semver-tags"],"published":"2023-02-06","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-03-25","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via improper input sanitization in the getGitTagsRemote function of the semver-tags npm package.","url":"https://insights.sbomify.com/CVE-2022-25853/"}