{"answers":{"affected":"3 open source packages ship an affected version, including gerapy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7698 in the wild and no public exploit code.","fix":"Upgrade gerapy to 0.9.3 or later.","what":"CVE-2020-7698 is a high-severity command injection vulnerability in Gerapy, published on 29 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7698 and fix it if it is affected.\n\nWhat it is: CVE-2020-7698 is a high-severity command injection vulnerability in Gerapy, published on 29 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-7698 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gerapy (PyPI): affected all versions; fixed in 0.9.3\n- gerapy (PyPI): affected all versions; fixed in 0.9.3\n- gerapy (PyPI): affected all versions; fixed in 0.9.3\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-2020-7698/ (Markdown: https://insights.sbomify.com/CVE-2020-7698/index.md)","id":"CVE-2020-7698","markdown":"https://insights.sbomify.com/CVE-2020-7698/index.md","name":"CVE-2020-7698","record":{"aliases":["GHSA-g57j-q48p-9vm2","PYSEC-2020-44","SNYK-PYTHON-GERAPY-572470"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Gerapy web application","requires_auth":"none","summary":"Attackers can execute arbitrary commands via unsanitized input in the project_configure endpoint of Gerapy.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"gerapy","vendor":"gerapy"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"This affects the package Gerapy from 0 and before 0.9.3. The input being passed to Popen, via the project_configure endpoint, isn’t being sanitized.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Command Injection","id":"CVE-2020-7698","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"Prototype Pollution","id":"CVE-2020-7699"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.3"],"introduced":["0"],"last_affected":[],"package":"gerapy","purl":null,"source":"GHSA-g57j-q48p-9vm2"},{"ecosystem":"PyPI","fixed":["0.9.3"],"introduced":["0"],"last_affected":[],"package":"gerapy","purl":"pkg:pypi/gerapy","source":"GHSA-g57j-q48p-9vm2"},{"ecosystem":"PyPI","fixed":["0.9.3"],"introduced":["0"],"last_affected":[],"package":"gerapy","purl":"pkg:pypi/gerapy","source":"PYSEC-2020-44"}],"prev":{"headline":"Command Injection","id":"CVE-2020-7697"},"products":["Gerapy"],"published":"2020-07-29","related":[{"cvss_score":9.8,"headline":"Gerapy may contain remote code execution vulnerability","id":"CVE-2021-43857","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.8,"headline":"Arbitrary command execution in Gerapy","id":"CVE-2021-32849","kev_date_added":null,"published":"2022-01-26"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via unsanitized input in the project_configure endpoint of Gerapy.","url":"https://insights.sbomify.com/CVE-2020-7698/"}