Controlled SSRF through URL in the WireMock
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub.
Summary
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. 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. 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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| wiremock | wiremock | org.wiremock:wiremock-webhooks-extension: >= 2.0.0, < 2.35.1; org.wiremock:wiremock-webhooks-extension: >= 3.0.0, < 3.0.3; wiremock-studio: All versions | — | No fix listed | CNA |
| — | org.wiremock:wiremock-webhooks-extension (Maven) | 3.0.0 to before 3.0.3 | 3.0.3 | Patch available | GHSA-hq8w-9w8w-pmx7 |
| — | org.wiremock:wiremock-webhooks-extension (Maven) | 2.0.0 to before 2.35.1 | 2.35.1 | Patch available | GHSA-hq8w-9w8w-pmx7 |
- wiremock Vendorwiremock Affected org.wiremock:wiremock-webhooks-extension: >= 2.0.0, < 2.35.1; org.wiremock:wiremock-webhooks-extension: >= 3.0.0, < 3.0.3; wiremock-studio: All versions Fixed in — No fix listed CNA
- org.wiremock:wiremock-webhooks-extension (Maven) Vendor— Affected 3.0.0 to before 3.0.3 Fixed in 3.0.3 Patch available GHSA-hq8w-9w8w-pmx7
- org.wiremock:wiremock-webhooks-extension (Maven) Vendor— Affected 2.0.0 to before 2.35.1 Fixed in 2.35.1 Patch available GHSA-hq8w-9w8w-pmx7
Remediation
- Fix · GHSA-hq8w-9w8w-pmx7 org.wiremock:wiremock-webhooks-extension (Maven) Fixed in 3.0.3 Advisory →
- Fix · GHSA-hq8w-9w8w-pmx7 org.wiremock:wiremock-webhooks-extension (Maven) Fixed in 2.35.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2023-41327
- 2026-10-03 Alias added: GHSA-hq8w-9w8w-pmx7
References
Advisory 2
More wiremock Studio vulnerabilities
- TI-2023-20860 Full read and controlled SSRF through URL parameter when testing a request inside wiremock-studio CVSS 3.1CRITICAL 10.0
- TI-2023-21929 Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio CVSS 3.1MEDIUM 6.6
Sources
- CVE-2023-41327 · CVE Program
- CVE-2023-41327 · NVD
- FIRST EPSS
- GHSA-hq8w-9w8w-pmx7 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences