{"answers":{"affected":"5 open source packages ship an affected version, including org.wiremock:wiremock-webhooks-extension and wiremock. It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-41327 in the wild and no public exploit code.","fix":"Upgrade org.wiremock:wiremock-webhooks-extension to a fixed version for your release line: 2.35.1 or 3.0.3.","what":"CVE-2023-41327 is a medium-severity server-side request forgery vulnerability in wiremock, published on 6 Sep 2023. 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-2023-41327 and fix it if it is affected.\n\nWhat it is: CVE-2023-41327 is a medium-severity server-side request forgery vulnerability in wiremock, published on 6 Sep 2023. 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-2023-41327 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.wiremock:wiremock-webhooks-extension (Maven): affected from 2.0.0; fixed in 2.35.1\n- org.wiremock:wiremock-webhooks-extension (Maven): affected from 2.0.0; fixed in 2.35.1\n- org.wiremock:wiremock-webhooks-extension (Maven): affected from 3.0.0; fixed in 3.0.3\n- org.wiremock:wiremock-webhooks-extension (Maven): affected from 3.0.0; fixed in 3.0.3\n- wiremock (Bitnami): affected from 2.0.0; fixed in 2.35.1, 3.0.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-2023-41327/ (Markdown: https://insights.sbomify.com/CVE-2023-41327/index.md)","id":"CVE-2023-41327","markdown":"https://insights.sbomify.com/CVE-2023-41327/index.md","name":"CVE-2023-41327","record":{"aliases":["BIT-wiremock-2023-41327","GHSA-hq8w-9w8w-pmx7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"WireMock HTTP mocking tool","requires_auth":"none","summary":"Attackers can bypass proxy restrictions in WireMock webhooks to send requests to internal services, potentially accessing sensitive data or bypassing security controls.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"studio","vendor":"wiremock"},{"product":"wiremock","vendor":"wiremock"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"WireMock is a tool for mocking HTTP services. WireMock can be configured to only permit proxying (and therefore recording) to certain addresses. This is achieved via a list of allowed address rules and a list of denied address rules, where the allowed list is evaluated first. \n\nUntil WireMock Webhooks Extension 3.0.0-beta-15, the filtering of target addresses from the proxy mode DID NOT work for Webhooks, so the users were potentially vulnerable regardless of the `limitProxyTargets` settings. Via the WireMock webhooks configuration, POST requests from a webhook might be forwarded to an arbitrary service reachable from WireMock’s instance. For example, If someone is running the WireMock docker Container inside a private cluster, they can trigger internal POST requests against unsecured APIs or even against secure ones by passing a token, discovered using another exploit, via authentication headers. This issue has been addressed in versions 2.35.1 and 3.0.3 of wiremock. Wiremock studio has been discontinued and will not see a fix. Users unable to upgrade should use external firewall rules to define the list of permitted destinations.","ecosystems":["Bitnami","Maven"],"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":"Controlled SSRF through URL in the WireMock","id":"CVE-2023-41327","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":5,"n_references":3,"next":{"headline":"Possibility limited SQL injection due to insufficient validation in Frappe","id":"CVE-2023-41328"},"packages":[{"ecosystem":"Bitnami","fixed":["2.35.1","3.0.3"],"introduced":["2.0.0","3.0.0"],"last_affected":[],"package":"wiremock","purl":"pkg:bitnami/wiremock","source":"BIT-wiremock-2023-41327"},{"ecosystem":"Maven","fixed":["2.35.1"],"introduced":["2.0.0"],"last_affected":[],"package":"org.wiremock:wiremock-webhooks-extension","purl":null,"source":"GHSA-hq8w-9w8w-pmx7"},{"ecosystem":"Maven","fixed":["2.35.1"],"introduced":["2.0.0"],"last_affected":[],"package":"org.wiremock:wiremock-webhooks-extension","purl":"pkg:maven/org.wiremock/wiremock-webhooks-extension","source":"GHSA-hq8w-9w8w-pmx7"},{"ecosystem":"Maven","fixed":["3.0.3"],"introduced":["3.0.0"],"last_affected":[],"package":"org.wiremock:wiremock-webhooks-extension","purl":null,"source":"GHSA-hq8w-9w8w-pmx7"},{"ecosystem":"Maven","fixed":["3.0.3"],"introduced":["3.0.0"],"last_affected":[],"package":"org.wiremock:wiremock-webhooks-extension","purl":"pkg:maven/org.wiremock/wiremock-webhooks-extension","source":"GHSA-hq8w-9w8w-pmx7"}],"prev":{"headline":"Account takeover via Kanban feature in GLPI","id":"CVE-2023-41326"},"products":["wiremock"],"published":"2023-09-06","related":[{"cvss_score":10,"headline":"Full read and controlled SSRF through URL parameter when testing a request inside wiremock-studio","id":"CVE-2023-39967","kev_date_added":null,"published":"2023-09-06"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["wiremock"]},"summary":"Attackers can bypass proxy restrictions in WireMock webhooks to send requests to internal services, potentially accessing sensitive data or bypassing security controls.","url":"https://insights.sbomify.com/CVE-2023-41327/"}