CVE-2023-41329
Vulnérabilité faible dans wiremock (wiremock)
Description
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.
Gravité et risque d'exploitation
CVE-2023-41329 obtient un score CVSS de 3.9/10, soit une gravité faible. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.63 %, ce qui la place devant 49.2 % des CVE référencées.
Que faire ?
- Vérifiez si wiremock (versions org.wiremock:wiremock: < 3.0.3, com.tomakehurst.wiremock:wiremock-jre8-standalone: < 2.35.1, wiremock/wiremock: < 2.35.1-1, pypi: wiremock: < 2.6.1, org.wiremock:wiremock-standalone: < 3.0.3, com.tomakehurst.wiremock:wiremock-jre8: < 2.35.1, wiremock/wiremock: >= 3.0.0, < 3.0.3-1) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.
