Medium, CVSS 4.6MavenPublished
WireMock Controlled Server Side Request Forgery vulnerability through URL
CVE-2023-41327 · GHSA-hq8w-9w8w-pmx7
- Affected
- Maven org.wiremock:wiremock-webhooks-extension >= 3.0.0, < 3.0.3; >= 2.0.0, < 2.35.1
- Fixed in
- 2.35.13.0.3· Vendor fix available
- Issue
- Impact 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. Documentation. Until 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. Affected components - WireMock Webhooks Extension 2.x versions until 2.35.1 (security patch) - WireMock 3.x version…
Recommended action: Upgrade to 3.0.3 or 2.35.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.