dbcve.org
Python WiremockApplication · Wiremock

CVE-2023-41329

MEDIUM · 6.6 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to 2.6.1 / 2.35.1 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
WireMock is a tool for mocking HTTP services. 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. This issue has been addressed in version 2.35.1 of wiremock-jre8 and wiremock-jre8-standalone, version 3.0.3 of wiremock and wiremock-standalone, version 2.6.1 of the python version of wiremock, and versions 2.35.1-1 and 3.0.3-1 of the wiremock/wiremock Docker container. Users are advised to upgrade. Users unable to upgrade should either configure firewall rules to define the list of permitted destinations or to configure WireMock to use IP addresses instead of the domain names.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WireMock's proxy mode network restrictions configured using domain names are vulnerable to DNS rebinding attacks due to a race condition where DNS resolution can change between initial validation and the actual outbound request, allowing attackers to bypass intended domain restrictions.

MitigationUpgrade to WireMock version 2.35.1+, 3.0.3+, or the corresponding Python/Docker versions. Alternatively, configure firewall rules or use IP addresses instead of domain names for restrictions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Python WiremockApplication
Affected:< 2.6.1
StudioApplication
Affected:<= 2.32.0-17
WiremockApplication
Affected:< 2.35.1>= 3.0.0, < 3.0.3
Wiremock DockerApplication
Affected:>= 2.0.0, < 2.35.1-1>= 3.0.0, < 3.0.3-1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the WireMock product in use
    Determine whether you are running WireMock Wiremock (Java), WireMock Docker, WireMock Studio, or Python Wiremock. Check your deployment artifacts, container images, or Python package.
    Affected if The product type determines which version range applies.
  2. Determine the installed version
    Run 'wiremock --version' for Java WireMock, check the Docker image tag or 'docker images', look at the Python package version with 'pip show wiremock', or check the Studio application version in the UI or logs.
    Affected if The version is below the fixed releases: WireMock (Java) < 2.35.1 or >= 3.0.0 but < 3.0.3; Docker < 2.35.1-1 or >= 3.0.0 but < 3.0.3-1; Python < 2.6.1; Studio <= 2.32.0-17.
  3. Check if proxy mode is enabled
    Inspect your WireMock configuration files (e.g., mappings/*.json, wiremock-admin.json) or startup parameters for 'proxy' or 'forward' settings. In the admin UI, check the Proxy section.
    Affected if Proxy mode is enabled and configured to forward requests to target URLs.
  4. Check if domain name restrictions are configured for proxy
    Review your proxy configuration for 'allowedDomains', 'domainRestrictions', or similar settings that specify domain names as targets for the proxy. Look for configuration keys that restrict outbound proxy destinations by domain name.
    Affected if Domain name-based restrictions are defined for the proxy (not IP-based).
  5. Compare your version against affected ranges
    Using the version identified in step 2, compare it against the affected ranges: WireMock/Java < 2.35.1 or >= 3.0.0 to < 3.0.3; Docker < 2.35.1-1 or >= 3.0.0 to < 3.0.3-1; Python < 2.6.1; Studio <= 2.32.0-17.
    Affected if Your installed version falls within any of the affected ranges and you have proxy mode with domain name restrictions configured.

You are affected if you are running any affected WireMock product version with proxy mode enabled and domain name-based network restrictions configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.1 / 2.35.1 / 2.35.1-1 or later
Fixed in 2.6.12.35.12.35.1-1
Interim mitigation

Upgrade to WireMock version 2.35.1+, 3.0.3+, or the corresponding Python/Docker versions. Alternatively, configure firewall rules or use IP addresses instead of domain names for restrictions.

Recommended fix High confidence

wiremock-jre8/wiremock-jre8-standalone: 2.35.1 | wiremock/wiremock-standalone 3.x: 3.0.3 | Python Wiremock: 2.6.1 | Docker: 2.35.1-1 or 3.0.3-1

  1. 1. Identify which WireMock product variant you are using (Java JRE8, standalone, Python, or Docker container)
  2. 2. For wiremock-jre8 or wiremock-jre8-standalone: upgrade to version 2.35.1
  3. 3. For wiremock or wiremock-standalone (version 3.x): upgrade to version 3.0.3
  4. 4. For Python Wiremock: upgrade to version 2.6.1
  5. 5. For wiremock/wiremock Docker container: upgrade to version 2.35.1-1 (for 2.x images) or 3.0.3-1 (for 3.x images)
  6. 6. If unable to upgrade, implement alternative mitigations: configure firewall rules to define permitted destinations, or configure WireMock to use IP addresses instead of domain names in network restrictions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Python Wiremock Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41329 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data