Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio webhooks, proxy and recorder modes
Impact
The proxy mode of WireMock, can be protected by the network restrictions configuration, as documented in Preventing proxying to and recording from specific target addresses. These restrictions can be configured using the domain names, and in such a case the configuration is vulnerable to the DNS rebinding attacks. A similar patch was applied in WireMock 3.0.0-beta-15 for the WireMock Webhook Extensions.
The root cause of the attack is a defect in the logic which allows for a race condition triggered by a DNS server whose address expires in between the initial validation and the outbound network request that might go to a domain that was supposed to be prohibited. Control over a DNS service is required to exploit this attack, so it has high execution complexity and limited impact.
Affected versions
- WireMock 3,x until 3.0.3 (security patch), on default settings in environments with access to the network
- WireMock 2.x until 2.35.1 (security patch), on default settings in environments with access to the network
- Python WireMock until 2.6.1
- WireMock Studio - all versions, this proprietary product was discontinued in 2022
Patches
- WireMock 3.0.3 + the 3.0.3-1 Docker image
- WireMock 2.35.1 + the 2.35.1-1 Docker image - backport to WireMock 2.x
- Python WireMock 2.6.1
Workarounds
For WireMock:
- Option 1: Configure WireMock to use IP addresses instead of the domain names in the outbound URLs subject to DNS rebinding
- Option 2: Use external firewall rules to define the list of permitted destinations
For WireMock Studio: N/A. Switch to another distribution, there will be no fix provided. The vendor of former WireMock Studio recommends migration to WireMock Cloud
References
- CVE-2023-41327 - Related issue in the WireMock Webhooks Extension
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | com.github.tomakehurst:wiremock-jre8 | < 2.35.1 | 2.35.1 |
| Java / Kotlin (Maven) | com.github.tomakehurst:wiremock-jre8-standalone | < 2.35.1 | 2.35.1 |
| Java / Kotlin (Maven) | org.wiremock:wiremock | < 3.0.3 | 3.0.3 |
| Java / Kotlin (Maven) | org.wiremock:wiremock-standalone | < 3.0.3 | 3.0.3 |
| Python (PyPI) | wiremock | < 2.6.1 | 2.6.1 |
References
- https://github.com/wiremock/wiremock/security/advisories/GHSA-pmxq-pj47-j8j4
- https://nvd.nist.gov/vuln/detail/CVE-2023-41329
- https://github.com/wiremock/wiremock
- https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses
- https://pypi.org/project/wiremock
- https://github.com/advisories/GHSA-pmxq-pj47-j8j4
- CVSS vector
CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L- Weakness (CWE)
CWE-290, CWE-350- Platform
- Java / Kotlin (Maven), Python (PyPI)
- Package
com.github.tomakehurst:wiremock-jre8, com.github.tomakehurst:wiremock-jre8-standalone, org.wiremock:wiremock- Disclosed
- 08.09.2023
- Updated
- 11.10.2026 13:20
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2026-2050 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-pmxq-pj47-j8j4 - CC BY 4.0
Vulnerability history: com.github.tomakehurst:wiremock-jre8-standalone
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.