[Snyk] Security upgrade org.apache.kafka:connect-runtime from 3.9.1 to 4.3.0

[d4v1de]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	HTTP Request Smuggling SNYK-JAVA-ORGECLIPSEJETTY-16061843	776	org.apache.kafka:connect-runtime: 3.9.1 -> 4.3.0 Major version upgrade Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[d4v1de]

The upgrade from Apache Kafka 3.9.1 to 4.3.0 is a major version change that introduces significant and mandatory breaking changes. This is a complex upgrade that requires careful planning and a multi-step migration process.

Key Breaking Changes:

• ZooKeeper Removal and KRaft Migration: Apache Kafka 4.0.0 and later have completely removed support for ZooKeeper. [1, 4, 7, 9] Clusters must be migrated to KRaft mode before upgrading to version 4.x. [4, 8] The recommended upgrade path involves first upgrading to a 3.x version that supports KRaft, performing the migration, and then upgrading to 4.x. [9]

• Java 17 Runtime Required: Kafka Connect, Brokers, and Tools now require Java 17 to run. [1, 4, 10] This is an increase from previous versions and requires an environment update.

• Kafka Connect API Removal: The REST API endpoint GET /connectors/{connector}/tasks-config has been removed in version 4.0.0. [1] Any scripts or automation using this endpoint must be updated to use its replacement, GET /connectors/{connector}/tasks. [1]

• Logging Framework Change: The logging framework has been migrated from Log4j to Log4j2. [1, 4] Existing Log4j configuration files must be converted to the Log4j2 format. [1]

• Deprecated API and Protocol Removal: Many client APIs and protocol versions deprecated in previous releases have been removed. [1, 2, 7] Clients, including Connect, must be on at least version 2.1 before the upgrade to ensure compatibility. [7]

Recommendation: This upgrade cannot be performed directly. A detailed migration plan is essential. Developers and operators must first migrate their existing cluster from ZooKeeper to KRaft mode on a 3.x version before attempting the upgrade to 4.3.0. The Java runtime environment must also be upgraded to Java 17. All custom tooling interacting with the Connect REST API must be validated and updated.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.