You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "AntChen27 (via GitHub)" <gi...@apache.org> on 2026/08/28 10:43:47 UTC

[I] [Improve][Zeta] Upgrade embedded Jetty and disable server version disclosure [seatunnel]

AntChen27 opened a new issue, #12002:
URL: https://github.com/apache/seatunnel/issues/12002

   ### What happened?
   
   The latest `dev` branch still pins Eclipse Jetty `9.4.56.v20240826`:
   
   - `seatunnel.shade.jetty.version`: `9.4.56.v20240826`
   - `jetty.version`: `9.4.56.v20240826`
   
   At commit `1ff72ceb3d2a823a0fca64ec009984d75e846c28`, `JettyService` also creates the HTTP connector using the default configuration:
   
   ```java
   ServerConnector httpConnector = new ServerConnector(server);
   ```
   
   Jetty therefore sends its exact version in every response by default:
   
   ```http
   Server: Jetty(9.4.56.v20240826)
   ```
   
   This exposes implementation details and causes version-based vulnerability scanners to report the following public advisories:
   
   - CVE-2025-5115 / GHSA-mmxm-8w33-wc4h
   - CVE-2024-6763 / GHSA-qh8g-58pp-2wxh
   
   I searched the repository and existing issues/PRs, but did not find a change covering either advisory or `setSendServerVersion(false)`.
   
   ### Affected versions
   
   - SeaTunnel 2.3.12
   - SeaTunnel 2.3.13
   - Latest `dev` as of 2026-08-28, commit `1ff72ceb3d2a823a0fca64ec009984d75e846c28`
   
   ### Security context
   
   This issue does not claim that both CVEs are exploitable in every SeaTunnel deployment:
   
   - CVE-2025-5115 requires HTTP/2. The current SeaTunnel `JettyService` creates a default HTTP/1.1 connector, so a standard deployment may not expose the vulnerable HTTP/2 path.
   - CVE-2024-6763 primarily affects applications that directly use Jetty `HttpURI` to validate attacker-controlled URLs. Jetty's normal server-side use of the class is not itself vulnerable according to the upstream advisory.
   
   However, the affected Jetty classes are embedded in the shaded SeaTunnel starter JAR, the exact vulnerable version is disclosed remotely, and there is currently no supported configuration to suppress the header.
   
   ### Expected behavior
   
   1. Upgrade or backport the embedded Jetty security fixes.
   2. Do not disclose the exact Jetty version in HTTP responses by default.
   3. Add a configuration option if retaining the current behavior is required for compatibility.
   4. Add a test asserting that REST responses do not contain an exact Jetty version.
   
   For the HTTP connector, the header can be disabled with an explicit `HttpConfiguration`:
   
   ```java
   HttpConfiguration httpConfig = new HttpConfiguration();
   httpConfig.setSendServerVersion(false);
   
   ServerConnector httpConnector =
           new ServerConnector(server, new HttpConnectionFactory(httpConfig));
   ```
   
   The HTTPS connector should use the same response-header policy.
   
   ### Upstream references
   
   - https://github.com/jetty/jetty.project/security/advisories/GHSA-mmxm-8w33-wc4h
   - https://github.com/jetty/jetty.project/security/advisories/GHSA-qh8g-58pp-2wxh
   - https://github.com/apache/seatunnel/blob/1ff72ceb3d2a823a0fca64ec009984d75e846c28/pom.xml#L73
   - https://github.com/apache/seatunnel/blob/1ff72ceb3d2a823a0fca64ec009984d75e846c28/pom.xml#L164
   - https://github.com/apache/seatunnel/blob/1ff72ceb3d2a823a0fca64ec009984d75e846c28/seatunnel-engine/seatunnel-engine-server/src/main/java/org/apache/seatunnel/engine/server/JettyService.java#L118
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Zeta] Upgrade embedded Jetty and disable server version disclosure [seatunnel]

Posted by "DanielLeens (via GitHub)" <gi...@apache.org>.
DanielLeens commented on issue #12002:
URL: https://github.com/apache/seatunnel/issues/12002#issuecomment-5525476095

   Thanks for stopping at the dependency boundary before opening a consumer PR. I rechecked current dev and the published Maven metadata: the main build currently resolves seatunnel-shade-jetty 9.4.56.v20240826-3.0.0, and 9.4.58.v20250814-3.0.0 is not published yet. The correct order is therefore: merge and release shade PR #22, wait until its exact coordinate is visible from Maven Central, then open the main-repository change that updates the root Jetty and shade properties together with the response-header regression test. Please do not add an alternate repository or a consumer POM change that cannot resolve in CI. Link both PRs and record the published coordinate in the consumer PR.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Zeta] Upgrade embedded Jetty and disable server version disclosure [seatunnel]

Posted by "davidzollo (via GitHub)" <gi...@apache.org>.
davidzollo commented on issue #12002:
URL: https://github.com/apache/seatunnel/issues/12002#issuecomment-5466664164

   Please submit a PR to solve this issue, thank you.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Zeta] Upgrade embedded Jetty and disable server version disclosure [seatunnel]

Posted by "DanielLeens (via GitHub)" <gi...@apache.org>.
DanielLeens commented on issue #12002:
URL: https://github.com/apache/seatunnel/issues/12002#issuecomment-5453909382

   Thanks for reporting this.
   
   Because this issue touches dependency security advisories and version-disclosure behavior, please report the full details privately to `security@apache.org` so the Apache security process can assess it there. To avoid expanding public exposure, let's keep further exploitability discussion and patch details off the public issue thread for now.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Zeta] Upgrade embedded Jetty and disable server version disclosure [seatunnel]

Posted by "CryoThrust (via GitHub)" <gi...@apache.org>.
CryoThrust commented on issue #12002:
URL: https://github.com/apache/seatunnel/issues/12002#issuecomment-5520881942

   I prepared the JettyService hardening and a response-header regression test. One dependency-release question surfaced before opening the PR: SeaTunnel consumes the separately published `org.apache.seatunnel:seatunnel-shade-jetty` artifact, and Maven Central currently exposes the 9.4.56 shaded artifact but not `9.4.58.v20250814-3.0.0`. Should this change be coordinated with a shade-artifact release, or is there an approved newer shaded Jetty version/repository I should target? I do not want to open a PR that cannot resolve its required dependency in CI.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Zeta] Upgrade embedded Jetty and disable server version disclosure [seatunnel]

Posted by "SEZ9 (via GitHub)" <gi...@apache.org>.
SEZ9 commented on issue #12002:
URL: https://github.com/apache/seatunnel/issues/12002#issuecomment-5476213837

   Thanks for the follow-up, @davidzollo. Agreed — a PR is the right next step here.
   
   To recap the scope from the earlier review, the PR should cover two things:
   
   1. **Upgrade the embedded Jetty from 9.4.56** to a version that addresses CVE-2025-5115 and CVE-2024-6763.
   2. **Disable the `Server` version header disclosure** in Zeta's JettyService, so the Jetty version is not exposed in HTTP responses.
   
   A couple of concrete asks for whoever picks this up:
   
   - Please keep both changes in the same PR (or clearly linked PRs) so the CVE remediation and the header hardening can be verified together.
   - In the PR description, note the exact Jetty version chosen and confirm it resolves both CVEs listed above.
   - Include a quick verification (e.g., a response header check) showing the `Server` header no longer leaks the version after the change.
   
   Happy to review once the PR is up. Thanks!
   
   <!-- streview-comment:701 -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Zeta] Upgrade embedded Jetty and disable server version disclosure [seatunnel]

Posted by "CryoThrust (via GitHub)" <gi...@apache.org>.
CryoThrust commented on issue #12002:
URL: https://github.com/apache/seatunnel/issues/12002#issuecomment-5520675554

   I will prepare a focused PR covering both requested parts: upgrade the embedded Jetty version to one addressing CVE-2025-5115 and CVE-2024-6763, and disable Jetty `Server` version disclosure for the Zeta HTTP/HTTPS connectors. I will include a response-header regression check and verify the selected version against the upstream advisories.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org