CVE-2023-41327
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2023-41327
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-41327.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2023-41327
- Aliases
- Published
- 2023-09-06T21:15:14Z
- Modified
- 2024-09-03T04:33:38.693942Z
- Severity
-
- 5.4 (Medium) CVSS_V3 - CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L CVSS Calculator
- Summary
- [none]
- Details
-
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
limitProxyTargetssettings. 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. - References
Affected packages
Git / github.com/tomakehurst/wiremock
Affected ranges
- Type
- GIT
- Repo
- https://github.com/tomakehurst/wiremock
- Events
- Type
- GIT
- Repo
- https://github.com/wiremock/wiremock
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed