{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20580 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20580 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20580 is a high-severity code injection vulnerability in n/a, published on 3 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-20580 and fix it if it is affected.\n\nWhat it is: CVE-2018-20580 is a high-severity code injection vulnerability in n/a, published on 3 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-20580 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-2018-20580/ (Markdown: https://insights.sbomify.com/CVE-2018-20580/index.md)","id":"CVE-2018-20580","markdown":"https://insights.sbomify.com/CVE-2018-20580/index.md","name":"CVE-2018-20580","record":{"aliases":["GHSA-rx49-4645-8575"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"API testing tool","requires_auth":"none","summary":"Remote attackers can execute arbitrary Java code in SmartBear ReadyAPI via crafted WSDL import requests.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"readyapi","vendor":"smartbear"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The WSDL import functionality in SmartBear ReadyAPI 2.5.0 and 2.6.0 allows remote attackers to execute arbitrary Java code via a crafted request parameter in a WSDL file.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-05-03","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-05-03T17:53:17Z","kind":"github_poc","ref":"https://github.com/gscamelo/CVE-2018-20580","stars":2,"title":"A proof of concept for ReadyAPI 2.5.0/2.6.0 Remote Code Execution Vulnerability."},{"date":"2019-05-06","kind":"exploitdb","ref":"46796","stars":null,"title":"ReadyAPI 2.5.0 / 2.6.0 - Remote Code Execution"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2018-20580","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2018-20582"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-20579"},"products":["n/a"],"published":"2019-05-03","related":[{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2020-12835","kev_date_added":null,"published":"2020-05-20"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2019-12180","kev_date_added":null,"published":"2020-02-05"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary Java code in SmartBear ReadyAPI via crafted WSDL import requests.","url":"https://insights.sbomify.com/CVE-2018-20580/"}