| Package | Affected versions | Patched versions |
|---|---|---|
| org.wiremock:wiremock-webhooks-extension | ≥ 2.0.0, < 2.35.1≥ 3.0.0, < 3.0.3 | 2.35.13.0.3 |
| studio | ≤ 2.32.0-17 | |
| wiremock | ≥ 2.0.0, < 2.35.1≥ 3.0.0, < 3.0.3 | 2.35.13.0.3 |
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.
NOTE: It was confirmed that WireMock Cloud does not expose sensitive internal APIs and hence not vulnerable to the issue. No action is needed if you use this SaaS distribution.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free