{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39967 exists.","fix":"No fix has been published for CVE-2023-39967 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-39967 is a critical server-side request forgery vulnerability in wiremock, published on 6 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-39967 and fix it if it is affected.\n\nWhat it is: CVE-2023-39967 is a critical server-side request forgery vulnerability in wiremock, published on 6 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39967 exists.\n\nAffected product: wiremock. 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-2023-39967/ (Markdown: https://insights.sbomify.com/CVE-2023-39967/index.md)","id":"CVE-2023-39967","markdown":"https://insights.sbomify.com/CVE-2023-39967/index.md","name":"CVE-2023-39967","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"end_of_life","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WireMock Studio","requires_auth":"none","summary":"Attackers can exploit SSRF in WireMock Studio to access internal services and read data via controlled URL parameters in request testing features.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"studio","vendor":"wiremock"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"WireMock is a tool for mocking HTTP services. When certain request URLs like “@127.0.0.1:1234\" are used in WireMock Studio configuration fields, the request might be forwarded to an arbitrary service reachable from WireMock’s instance. There are 3 identified potential attack vectors: via “TestRequester” functionality, webhooks and the proxy mode. As we can control HTTP Method, HTTP Headers, HTTP Data, it allows sending requests with the default level of credentials for the WireMock instance. The vendor has discontinued the affected Wiremock studio product and there will be no fix. Users are advised to find alternatives.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Full read and controlled SSRF through URL parameter when testing a request inside wiremock-studio","id":"CVE-2023-39967","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Open Redirect Vulnerability in jupyter-server","id":"CVE-2023-39968"},"packages":[],"prev":{"headline":"1Panel arbitrary file write vulnerability exists in the background","id":"CVE-2023-39966"},"products":["wiremock"],"published":"2023-09-06","related":[{"cvss_score":4.6,"headline":"Controlled SSRF through URL in the WireMock","id":"CVE-2023-41327","kev_date_added":null,"published":"2023-09-06"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["wiremock"]},"summary":"Attackers can exploit SSRF in WireMock Studio to access internal services and read data via controlled URL parameters in request testing features.","url":"https://insights.sbomify.com/CVE-2023-39967/"}