-
Notifications
You must be signed in to change notification settings - Fork 24
chore: upgrade WireMock to 4.0.0-beta.32 to resolve Jetty CVE-2025-11143#332
Draft
Copilot wants to merge 2 commits into
Draft
chore: upgrade WireMock to 4.0.0-beta.32 to resolve Jetty CVE-2025-11143 #332Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
Codecov Report
✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 38.05%. Comparing base (2565cc8) to head (1564851).
Additional details and impacted files
@@ Coverage Diff @@ ## main #332 +/- ## ========================================= Coverage 38.05% 38.05% Complexity 1259 1259 ========================================= Files 198 198 Lines 7646 7646 Branches 885 885 ========================================= Hits 2910 2910 Misses 4598 4598 Partials 138 138
☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.
🚀 New features to boost your workflow:
- ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
Agent-Logs-Url: https://github.com/openfga/java-sdk/sessions/f0440740-2bed-4707-be8f-7f5412017012 Co-authored-by: curfew-marathon <98830296+curfew-marathon@users.noreply.github.com>
Copilot
AI
changed the title
(削除) [WIP] Fix parsing of invalid URIs in Jetty (削除ここまで)
(追記) fix(deps): upgrade WireMock to 4.0.0-beta.32 to resolve Jetty CVE-2025-11143 (追記ここまで)
Apr 24, 2026
@curfew-marathon
curfew-marathon
changed the title
(削除) fix(deps): upgrade WireMock to 4.0.0-beta.32 to resolve Jetty CVE-2025-11143 (削除ここまで)
(追記) chore: upgrade WireMock to 4.0.0-beta.32 to resolve Jetty CVE-2025-11143 (追記ここまで)
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
GHSA-wjpw-4j6x-6rwh / CVE-2025-11143: all Jetty 11.x versions (
>= 11.0.0, <= 11.0.26) have differential URI parsing behaviour that can bypass security controls in multi-component systems. Jetty 11.x is EOL with no patch on Maven Central; patched versions start at 12.0.31 / 12.1.5.Changes
build.gradle: bumporg.wiremock:wiremock3.13.2→4.0.0-beta.32, which pulls injetty-bom:12.1.8(patched)build.gradle: addorg.wiremock:wiremock-junit5:4.0.0-beta.32— WireMock 4.x splits the JUnit 5 extension into a separate artifact; no test source changes needed since thecom.github.tomakehurst.wiremock.*namespace is preservedReachability
WireMock is a test-only mock server. Jetty's URI parser is never in the request path for any production or security-sensitive logic. This update resolves the scanner alert; there is no active exploit risk in this codebase.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
invalid-hostname-that-does-not-exist.local/usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java -Dorg.gradle.internal.worker.tmpdir=/home/REDACTED/work/java-sdk/java-sdk/build/tmp/test/work -javaagent:/home/REDACTED/work/java-sdk/java-sdk/build/tmp/.cache/expanded/zip_27729b840c216bdc69a9315e04b27ab1/jacocoagent.jar=destfile=build/jacoco/test.exec,append=true,inclnolocationclasses=false,dumponexit=true,output=file,jmx=false @/home/REDACTED/.gradle/.tmp/gradle-worker-classpath4853964645954119057txt -Xmx512m -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -ea worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test Executor 1'(dns block)wiremock.org/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
This section details the Dependabot vulnerability alert you should resolve
<alert_title>org.eclipse.jetty:jetty-http has different parsing of invalid URIs</alert_title>
<alert_description>The Jetty URI parser has some key differences compared to other common parsers when evaluating invalid or unusual URIs. Specifically:
Invalid Scheme
https>://vulndetector.com/pathhttp>httpsImproper IPv4 mapped IPv6
http://[0:0:0:0:0:ffff:127.0.0.1][::ffff:127.0.0.1][::ffff:127.0.0.1]http://[::ffff:255.255.0.0][::ffff:255.255.0.0][::ffff:255.255.0.0]Incorrect IPv6 delimeter priority
http://[normal.com@]vulndetector.com/[normal.com@]http://normal.com[user@vulndetector].com/normal.comhttp://normal.com[@]vulndetector.com/normal.comIncorrect delimeter priority
http://normal.com/#@vulndetector.comvulndetector.comnormal.comnormal.comhttp://normal.com/?@vulndetector.comvulndetector.comnormal.comnormal.comImpact
Differential parsing of URIs in systems using multiple components may result in security by-pass. For example a component that enforces a black list may interpret the URIs differently from one that generates a response.
At the very least, differential parsing may divulge implementation details.
Patches
Patched in Supported Open Source versions.
Workarounds
None
Resources
low
https://github.com/jetty/jetty.project/security/advisories/GHSA-wjpw-4j6x-6rwh https://nvd.nist.gov/vuln/detail/CVE-2025-11143 https://github.com/user-attachments/files/22222625/Java.Eclipse.Jetty.Report_.Incorrect.Parsing.Priority.of.the.IPv6.Hostname.Delimeter.pdf https://github.com/user-attachments/files/22222626/Java.Eclipse.Jetty.Report_.The.Parsing.Priority.of.the.Delimiter.pdf https://github.com/user-attachments/files/22222627/Java.Eclipse.Jetty.Report_.Parsing.Difference.Due.to.Deformed.Scheme.pdf https://github.com/user-attachments/files/22222630/Java.Eclipse.Jetty.Report_.Improper.IPv4-mapped.IPv6.Parsing.pdf https://github.com/advisories/GHSA-wjpw-4j6x-6rwhGHSA-wjpw-4j6x-6rwh, CVE-2025-11143
org.eclipse.jetty:jetty-http
maven
<vulnerable_versions>= 11.0.26</vulnerable_versions>
<patched_version></patched_version>
<manifest_path>settings.gradle</manifest_path>
<task_instructions>Resolve this alert by updating the affected package to a non-vulnerable version. Prefer the lowest non-vulnerable version (see the patched_version field above) over the latest to minimize breaking changes. Include a Reachability Assessment section in the PR description. Review the alert_description field to understand which APIs, features, or configurations are affected, then search the codebase for usage of those specific items. If the vulnerable code path is reachable, explain how (which files, APIs, or call sites use the affected functionality) and note that the codebase is actively exposed...