Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-290.
Summary
WireMock is a tool for mocking HTTP services. 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. This issue has been addressed in version 2.35.1 of wiremock-jre8 and wiremock-jre8-standalone, version 3.0.3 of wiremock and wiremock-standalone, version 2.6.1 of the python version of wiremock, and versions 2.35.1-1 and 3.0.3-1 of the wiremock/wiremock Docker container. Users are advised to upgrade. Users unable to upgrade should either configure firewall rules to define the list of permitted destinations or to configure WireMock to use IP addresses instead of the domain names.
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: < 3.0.3; org.wiremock:wiremock-standalone: < 3.0.3; com.tomakehurst.wiremock:wiremock-jre8: < 2.35.1; com.tomakehurst.wiremock:wiremock-jre8-standalone: < 2.35.1; pypi: wiremock: < 2.6.1; wiremock/wiremock: < 2.35.1-1; wiremock/wiremock: >= 3.0.0, < 3.0.3-1 | — | No fix listed | CNA |
| — | org.wiremock:wiremock-standalone (Maven) | before 3.0.3 | 3.0.3 | Patch available | GHSA-pmxq-pj47-j8j4 |
| — | org.wiremock:wiremock (Maven) | before 3.0.3 | 3.0.3 | Patch available | GHSA-pmxq-pj47-j8j4 |
| — | com.github.tomakehurst:wiremock-jre8 (Maven) | before 2.35.1 | 2.35.1 | Patch available | GHSA-pmxq-pj47-j8j4 |
| — | com.github.tomakehurst:wiremock-jre8-standalone (Maven) | before 2.35.1 | 2.35.1 | Patch available | GHSA-pmxq-pj47-j8j4 |
| — | wiremock (PyPI) | before 2.6.1 | 2.6.1 | Patch available | GHSA-pmxq-pj47-j8j4 |
- wiremock Vendorwiremock Affected org.wiremock:wiremock: < 3.0.3; org.wiremock:wiremock-standalone: < 3.0.3; com.tomakehurst.wiremock:wiremock-jre8: < 2.35.1; com.tomakehurst.wiremock:wiremock-jre8-standalone: < 2.35.1; pypi: wiremock: < 2.6.1; wiremock/wiremock: < 2.35.1-1; wiremock/wiremock: >= 3.0.0, < 3.0.3-1 Fixed in — No fix listed CNA
- org.wiremock:wiremock-standalone (Maven) Vendor— Affected before 3.0.3 Fixed in 3.0.3 Patch available GHSA-pmxq-pj47-j8j4
- org.wiremock:wiremock (Maven) Vendor— Affected before 3.0.3 Fixed in 3.0.3 Patch available GHSA-pmxq-pj47-j8j4
- com.github.tomakehurst:wiremock-jre8 (Maven) Vendor— Affected before 2.35.1 Fixed in 2.35.1 Patch available GHSA-pmxq-pj47-j8j4
- com.github.tomakehurst:wiremock-jre8-standalone (Maven) Vendor— Affected before 2.35.1 Fixed in 2.35.1 Patch available GHSA-pmxq-pj47-j8j4
- wiremock (PyPI) Vendor— Affected before 2.6.1 Fixed in 2.6.1 Patch available GHSA-pmxq-pj47-j8j4
CPE configurations NVD · 4
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:wiremock:python_wiremock:*:*:*:*:*:*:*:* | before 2.6.1 | Vulnerable | wiremock |
| cpe:2.3:a:wiremock:studio:*:*:*:*:*:*:*:* | up to 2.32.0-17 | Vulnerable | wiremock |
| cpe:2.3:a:wiremock:wiremock:*:*:*:*:*:*:*:* | before 2.35.1; 3.0.0 to before 3.0.3 | Vulnerable | wiremock |
| cpe:2.3:a:wiremock:wiremock_docker:*:*:*:*:*:*:*:* | 2.0.0 to before 2.35.1-1; 3.0.0 to before 3.0.3-1 | Vulnerable | wiremock |
- cpe:2.3:a:wiremock:python_wiremock:*:*:*:*:*:*:*:* Versions before 2.6.1 Vulnerable ·wiremock
- cpe:2.3:a:wiremock:studio:*:*:*:*:*:*:*:* Versions up to 2.32.0-17 Vulnerable ·wiremock
- cpe:2.3:a:wiremock:wiremock:*:*:*:*:*:*:*:* Versions before 2.35.1; 3.0.0 to before 3.0.3 Vulnerable ·wiremock
- cpe:2.3:a:wiremock:wiremock_docker:*:*:*:*:*:*:*:* Versions 2.0.0 to before 2.35.1-1; 3.0.0 to before 3.0.3-1 Vulnerable ·wiremock
Remediation
- Fix · GHSA-pmxq-pj47-j8j4 org.wiremock:wiremock-standalone (Maven) Fixed in 3.0.3 Advisory →
- Fix · GHSA-pmxq-pj47-j8j4 org.wiremock:wiremock (Maven) Fixed in 3.0.3 Advisory →
- Fix · GHSA-pmxq-pj47-j8j4 com.github.tomakehurst:wiremock-jre8 (Maven) Fixed in 2.35.1 Advisory →
- Fix · GHSA-pmxq-pj47-j8j4 com.github.tomakehurst:wiremock-jre8-standalone (Maven) Fixed in 2.35.1 Advisory →
- Fix · GHSA-pmxq-pj47-j8j4 wiremock (PyPI) Fixed in 2.6.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2023-41329
- 2026-10-03 Alias added: GHSA-pmxq-pj47-j8j4
- 2026-10-28 EPSS moved to the 50th–90th percentile
References
Sources
- CVE-2023-41329 · CVE Program
- CVE-2023-41329 · NVD
- FIRST EPSS
- GHSA-pmxq-pj47-j8j4 · 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