Skip to content
Fencer Vulns
low 3.9

CVE-2023-41329 json

Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio

published 2023-09-06 3 y ago modified 2026-09-10 1 mo ago also BIT-wiremock-2023-41329 , EUVD-2023-2564 , GHSA-pmxq-pj47-j8j4 , PYSEC-2026-2050

cvss
3.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

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.

Patch / fix

  • maven org.wiremock:wiremock-standalone 3.0.3
  • maven org.wiremock:wiremock 3.0.3
  • maven com.github.tomakehurst:wiremock-jre8 2.35.1
  • maven com.github.tomakehurst:wiremock-jre8-standalone 2.35.1
  • pypi wiremock 2.6.1
  • bitnami wiremock 2.35.1, 3.0.3
  • wiremock python_wiremock 2.6.1
  • wiremock wiremock 2.35.1, 3.0.3
  • wiremock wiremock_docker 2.35.1-1, 3.0.3-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.9 CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
GitHub 3.1 3.9 CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
NVD 3.1 6.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 6.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 3.9 CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
maven org.wiremock:wiremock-standalone
<3.0.3
3.0.3
maven org.wiremock:wiremock
<3.0.3
3.0.3
maven com.github.tomakehurst:wiremock-jre8
<2.35.1
2.35.1
maven com.github.tomakehurst:wiremock-jre8-standalone
<2.35.1
2.35.1
pypi wiremock
<2.6.1
2.6.1
bitnami wiremock
<2.35.1
>=3.0.0, <3.0.3
2.35.1
3.0.3

Affected products

  • wiremock wiremock

Classification

Weakness
  • CWE-290 Authentication Bypass by Spoofing
  • CWE-350 Reliance on Reverse DNS Resolution for a Security-Critical Action

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.