CVE-2023-41327
What it is
WireMock is a tool for mocking HTTP services. 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. 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. This issue has been addressed in versions 2.35.1 and 3.0.3 of wiremock. Wiremock studio has been discontinued and will not see a fix. Users unable to upgrade should use external firewall rules to define the list of permitted destinations.
At a glance
- Exploitability
- Can be exploited from the same network segment without logging in, but needs a user to act. Limited direct impact.
- Exploit odds
- 0.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.5% in the next 30 days (EPSS).
- Severity: 4.6 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.5% · EPSS, next 30 days
- Weakness
- CWE-918 · Server-side request forgery
- Record status
- Modified
Affected
- Wiremock Studio ≤ 2.32.0-17
- Wiremock < 2.35.1
- Wiremock < 3.0.3
Attack profile CVSS 3.1 · 4.6
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-41327.md and follow it. Check whether this project is affected by CVE-2023-41327. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/wiremock/wiremock/releases/tag/3.0.0-beta-15
- https://github.com/wiremock/wiremock/security/advisories/GHSA-hq8w-9w8w-pmx7
- https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses
- https://github.com/wiremock/wiremock/releases/tag/3.0.0-beta-15
- https://github.com/wiremock/wiremock/security/advisories/GHSA-hq8w-9w8w-pmx7
- https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses
References
- https://github.com/wiremock/wiremock/releases/tag/3.0.0-beta-15
- https://github.com/wiremock/wiremock/security/advisories/GHSA-hq8w-9w8w-pmx7
- https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses
- https://github.com/wiremock/wiremock/releases/tag/3.0.0-beta-15
- https://github.com/wiremock/wiremock/security/advisories/GHSA-hq8w-9w8w-pmx7
- https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses