GitHub Advisoryadvisory · Maven
GHSA-hq8w-9w8w-pmx7 WireMock Controlled Server Side Request Forgery vulnerability through URL
MEDIUM
Official page ↗
- Aliases
- CVE-2023-41327
- Ecosystem
- Maven
- Packages
- org.wiremock:wiremock-webhooks-extension
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
- Weaknesses
- CWE-918
- Reviewed
- 2023-09-06
Affected packages
• Maven org.wiremock:wiremock-webhooks-extension: >= 3.0.0, < 3.0.3 → fixed in 3.0.3
• Maven org.wiremock:wiremock-webhooks-extension: >= 2.0.0, < 2.35.1 → fixed in 2.35.1
Description
Impact
WireMock can be configured to only permit proxying (and therefore recording) to certain addresses. This is achieved via a list of allowed address rules and a list of denied address rules, where the allowed list is evaluated first. Documentation.
Until WireMock Webhooks Extension 3.0.0-beta-15, the filtering of target addresses from the proxy mode DID NOT work for Webhooks, so the users were potentially vulnerable regardless of the `limitProxyTargets` settings.
Via the WireMock webhooks configuration, POST requests from a webhook might be forwarded to an arbitrary service reachable from WireMock’s instance. For example, If someone is running the WireMock docker Container inside a private cluster, they can trigger internal POST requests against unsecured APIs or even against secure ones by passing a token, discovered using another exploit, via authentication headers.
Affected components
• WireMock Webhooks Extension 2.x versions until 2.35.1 (security patch)
• WireMock 3.x version until 3.0.3 (security patch)
• All versions of WireMock Studio (discontinued). This distribution bundles the WireMock Webhooks Extension and activates it by default
Patches and Mitigation
• For WireMock 2.x and 3.x - upgrade to the versions with the security patches
• Setup network restrictions similarly to https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses
• For WireMock Studio: Stop using discontinued WireMock Studio, migrate to other distributions. The vendor of WireMock Studio recommends migration to WireMock Cloud
NOTE: It was confirmed that WireMock Cloud does not expose sensitive internal APIs and hence not vulnerable to the issue. No action is needed if you use this SaaS distribution.
Workarounds
• Use external firewall rules to define the list of permitted destinations
References
• CVE-2023-39967
• Preventing proxying to and recording from specific target addresses
Credits
• @W0rty for reporting CVE-2023-39967 in WireMock Studio
• WireMock Inc. team for discovering similar exploits in Webhooks and the risk in the Proxy mode defaults for WireMock
Related
Alias · CVE (1)
- CVE-2023-41327 WireMock is a tool for mocking HTTP services. vulnerability
Weakness · CWE (1)
- CWE-918 Server-Side Request Forgery weakness
References
- https://github.com/wiremock/wiremock/security/advisories/GHSA-hq8w-9w8w-pmx7 web
- https://nvd.nist.gov/vuln/detail/CVE-2023-41327 advisory
- https://github.com/wiremock/wiremock package
- https://github.com/wiremock/wiremock/releases/tag/2.35.1 web
- https://github.com/wiremock/wiremock/releases/tag/3.0.0-beta-15 web
- https://github.com/wiremock/wiremock/releases/tag/3.0.3 web
- https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses web