CVE-2023-41329
published 2023-09-06CVE-2023-41329: WireMock is a tool for mocking HTTP services. The proxy mode of WireMock, can be protected by the network restrictions configuration, as documented in…
PriorityP337medium6.6CVSS 3.1
AVNACHPRHUINSUCHIHAH
EPSS
0.57%
42.9th percentile
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.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| wiremock | python_wiremock | < 2.6.1 | 2.6.1 |
| wiremock | studio | <= 2.32.0-17 | — |
| wiremock | wiremock | < 2.35.1 | 2.35.1 |
| wiremock | wiremock | — | — |
| wiremock | wiremock | — | — |
| wiremock | wiremock | — | — |
| wiremock | wiremock | — | — |
| wiremock | wiremock | — | — |
| wiremock | wiremock | — | — |
| wiremock | wiremock | — | — |
| wiremock | wiremock | >= 0 < 2.6.1 | 2.6.1 |
| wiremock | wiremock | >= 3.0.0 < 3.0.3 | 3.0.3 |
| wiremock | wiremock_docker | >= 2.0.0 < 2.35.1-1 | 2.35.1-1 |
| wiremock | wiremock_docker | >= 3.0.0 < 3.0.3-1 | 3.0.3-1 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio webhooks, proxy and recorder modes
osv·2023-09-08
CVE-2023-41329 [LOW] Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio webhooks, proxy and recorder modes
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](https://wiremock.org/docs/configuration/#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 init
GHSA
Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio webhooks, proxy and recorder modes
ghsa·2023-09-08
CVE-2023-41329 [LOW] CWE-290 Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio webhooks, proxy and recorder modes
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](https://wiremock.org/docs/configuration/#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 init
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/wiremock/wiremock/security/advisories/GHSA-pmxq-pj47-j8j4https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresseshttps://github.com/wiremock/wiremock/security/advisories/GHSA-pmxq-pj47-j8j4https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses
2023-09-06
Published