← Back
CVE-2023-41329
Vulnerability in wiremock (CVE-2023-41329)
Summary
vulnerability in wiremock (CVE-2023-41329). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.35.1, 3.0.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-41329** has been found in wiremock.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade wiremock to **2.35.1, 3.0.3** or later.
If unsure, ask your IT team or search "wiremock CVE-2023-41329" on the vendor's site.
CVE-2023-41329 (wiremock) — CWE-290 /
Attack vector: adjacent-network / no user interaction
Patched: `2.35.1, 3.0.3` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-290) exists in wiremock.
📍 Affected scope
wiremock — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.35.1, 3.0.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'wiremock' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wiremock' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `wiremock` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade wiremock to 2.35.1, 3.0.3ステージング環境で 2.35.1, 3.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
wiremock
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.35.1"},{"introduced":"3.0.0"},{"fixed":"3.0.3"}]}]
Maven
org.wiremock:wiremock-standalone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.3"}]}]
Maven
org.wiremock:wiremock
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.3"}]}]
Maven
com.github.tomakehurst:wiremock-jre8
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.35.1"}]}]
Maven
com.github.tomakehurst:wiremock-jre8-standalone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.35.1"}]}]
PyPI
wiremock
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2023-41329
- advisory https://github.com/advisories/GHSA-pmxq-pj47-j8j4
- package https://github.com/wiremock/wiremock
- package https://pypi.org/project/wiremock
- web https://github.com/wiremock/wiremock/security/advisories/GHSA-pmxq-pj47-j8j4
- web https://wiremock.org/docs/configuration/#preventing-proxying-to-and-recording-from-specific-target-addresses