Update dependency com.github.tomakehurst:wiremock-jre8 to v2.35.1 [SECURITY] (master)

[renovatebot-confluentinc]

For any questions/concerns about this PR, please review the Renovate Bot wiki/FAQs, or the #renovatebot Slack channel.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.github.tomakehurst:wiremock-jre8 (source)	2.30.1 -> 2.35.1

GitHub Vulnerability Alerts

CVE-2023-41329

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

---

Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio webhooks, proxy and recorder modes

CVE-2023-41329 / GHSA-pmxq-pj47-j8j4

More information

Details

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

Severity

• CVSS Score: 3.9 / 10 (Low)
• Vector String: CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

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

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[sonarqube-confluent]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• No coverage information (0.00% Estimated after merge)
• No duplication information (0.00% Estimated after merge)

Project ID: kafka-connect-elasticsearch

View in SonarQube