{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5236 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5236 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5236 is a high-severity vulnerability in Rapid7 AppSpider Pro, published on 3 May 2017. 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-2017-5236 and fix it if it is affected.\n\nWhat it is: CVE-2017-5236 is a high-severity vulnerability in Rapid7 AppSpider Pro, published on 3 May 2017. 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-2017-5236 in the wild and no public exploit code.\n\nAffected product: Rapid7 AppSpider Pro. 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-2017-5236/ (Markdown: https://insights.sbomify.com/CVE-2017-5236/index.md)","id":"CVE-2017-5236","markdown":"https://insights.sbomify.com/CVE-2017-5236/index.md","name":"CVE-2017-5236","record":{"aliases":["GHSA-jxg9-2w2r-prxg"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rapid7 AppSpider Pro","requires_auth":"none","summary":"Attackers can execute arbitrary code by placing a malicious DLL in the installer's working directory, affecting Rapid7 AppSpider Pro users.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"appspider_pro","vendor":"rapid7"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"Editions of Rapid7 AppSpider Pro installers prior to version 6.14.060 contain a DLL preloading vulnerability, wherein it is possible for the installer to load a malicious DLL located in the current working directory of the installer.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in AppSpider Pro","id":"CVE-2017-5236","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in EV-07S GPS Tracker","id":"CVE-2017-5237"},"packages":[],"prev":{"headline":"Other in Metasploit Pro","id":"CVE-2017-5235"},"products":["AppSpider Pro"],"published":"2017-05-03","related":[{"cvss_score":7.8,"headline":"Other in AppSpider Pro","id":"CVE-2017-5233","kev_date_added":null,"published":"2017-03-02"},{"cvss_score":7.5,"headline":"Memory corruption in AppSpider Pro","id":"CVE-2017-5240","kev_date_added":null,"published":"2017-05-03"},{"cvss_score":4.6,"headline":"Cross-site scripting in AppSpider Pro","id":"CVE-2025-4951","kev_date_added":null,"published":"2025-05-20"},{"cvss_score":3.3,"headline":"Rapid7 AppSpider Project Name Validation Bypass","id":"CVE-2025-11195","kev_date_added":null,"published":"2025-09-30"},{"cvss_score":3.3,"headline":"Rapid7 Appspider Broken Access Control Vulnerability","id":"CVE-2025-36857","kev_date_added":null,"published":"2025-09-25"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Rapid7"]},"summary":"Attackers can execute arbitrary code by placing a malicious DLL in the installer's working directory, affecting Rapid7 AppSpider Pro users.","url":"https://insights.sbomify.com/CVE-2017-5236/"}