{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-28790 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-28790 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-28790 is a high-severity command injection vulnerability in n/a, published on 18 Mar 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-28790 and fix it if it is affected.\n\nWhat it is: CVE-2021-28790 is a high-severity command injection vulnerability in n/a, published on 18 Mar 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-28790 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2021-28790/ (Markdown: https://insights.sbomify.com/CVE-2021-28790/index.md)","id":"CVE-2021-28790","markdown":"https://insights.sbomify.com/CVE-2021-28790/index.md","name":"CVE-2021-28790","record":{"aliases":["GHSA-7qqp-g74r-7vjv"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VS Code extension","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious workspace with a crafted configuration in the SwiftLint VS Code extension.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"swiftlint","vendor":"swiftlint_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"The unofficial SwiftLint extension before 1.4.5 for Visual Studio Code allows remote attackers to execute arbitrary code by constructing a malicious workspace with a crafted swiftlint.path configuration value that triggers execution upon opening the workspace.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Command injection in n/a","id":"CVE-2021-28790","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2021-28791"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2021-28789"},"products":["n/a"],"published":"2021-03-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious workspace with a crafted configuration in the SwiftLint VS Code extension.","url":"https://insights.sbomify.com/CVE-2021-28790/"}