{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-12180 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12180 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12180 is a high-severity code injection vulnerability in n/a, published on 5 Feb 2020. 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-2019-12180 and fix it if it is affected.\n\nWhat it is: CVE-2019-12180 is a high-severity code injection vulnerability in n/a, published on 5 Feb 2020. 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-2019-12180 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-2019-12180/ (Markdown: https://insights.sbomify.com/CVE-2019-12180/index.md)","id":"CVE-2019-12180","markdown":"https://insights.sbomify.com/CVE-2019-12180/index.md","name":"CVE-2019-12180","record":{"aliases":["GHSA-mvpr-q6w5-8529"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"API testing tool","requires_auth":"none","summary":"Attackers can execute arbitrary Groovy code on victim machines by tricking users into opening malicious project files in ReadyAPI or SoapUI.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"readyapi","vendor":"smartbear"},{"product":"soapui","vendor":"smartbear"}],"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":"An issue was discovered in SmartBear ReadyAPI through 2.8.2 and 3.0.0 and SoapUI through 5.5. When opening a project, the Groovy \"Load Script\" is automatically executed. This allows an attacker to execute arbitrary Groovy Language code (Java scripting language) on the victim machine by inducing it to open a malicious Project. The same issue is present in the \"Save Script\" function, which is executed automatically when saving a project.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-01-20","github_poc":1,"max_poc_stars":4,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-01-20T17:33:23Z","kind":"github_poc","ref":"https://github.com/0x-nope/CVE-2019-12180","stars":4,"title":"Advisory \u0026 PoC"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2019-12180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2019-12181"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-12177"},"products":["n/a"],"published":"2020-02-05","related":[{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2020-12835","kev_date_added":null,"published":"2020-05-20"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2018-20580","kev_date_added":null,"published":"2019-05-03"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary Groovy code on victim machines by tricking users into opening malicious project files in ReadyAPI or SoapUI.","url":"https://insights.sbomify.com/CVE-2019-12180/"}