[Snyk] Fix for 1 vulnerabilities

[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
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-18517159	828	com.fasterxml.jackson.dataformat:jackson-dataformat-csv: 2.10.0 -> 2.18.8 org.apache.kafka:connect-runtime: 2.6.2 -> 4.0.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:

🦉 Allocation of Resources Without Limits or Throttling

[d4v1de]

This upgrade includes a major version jump for org.apache.kafka:connect-runtime from 2.6.2 to 4.0.0, which introduces significant and mandatory breaking changes. The jackson-dataformat-csv upgrade is considered low risk.

org.apache.kafka:connect-runtime@2.6.2 → 4.0.0 (HIGH RISK)

This is a major upgrade that requires careful planning and a multi-step migration. Direct upgrade is not possible.

Key Breaking Changes:

• ZooKeeper Removal: Kafka 4.0.0 completely removes support for ZooKeeper, making KRaft (Kafka Raft Metadata mode) the only option. [1, 4, 6, 18] Clusters currently using ZooKeeper must be migrated to KRaft before upgrading to version 4.0. [4]
• Java Runtime Requirement: Kafka Brokers, Connect, and Tools now require Java 17 to run. [1, 7, 16] This is an upgrade from Java 8, which was deprecated in Kafka 3.0. [2, 3]
• API and Protocol Removals: Legacy APIs and client protocols deprecated for over a year have been removed. [1, 4, 6] Before upgrading clients to 4.0, brokers must be at version 2.1 or higher. [16]
• Logging Framework: The logging framework has been migrated from Log4j to Log4j2, which requires converting existing configuration files. [1, 16]
• Default Behavior Changes: The upgrade path crosses Kafka 3.0, which changed producer defaults to enable stronger delivery guarantees (acks=all, enable.idempotence=true). [2, 3]

Recommendation:
A direct upgrade is not feasible. A phased migration is required:

1. First, upgrade your cluster to a 3.x version that supports both ZooKeeper and KRaft (e.g., 3.6.x or 3.7.x). [4, 18]
2. Migrate your cluster from ZooKeeper to KRaft mode.
3. Ensure your environment is running on Java 17.
4. Finally, upgrade to Kafka 4.0.0.

com.fasterxml.jackson.dataformat:jackson-dataformat-csv@2.10.0 → 2.18.8 (LOW RISK)

This upgrade spans several minor versions within the same major release. No significant breaking API changes are documented for this range. The Jackson 2.18 release notes indicate performance improvements and the removal of synchronization from CsvMapper, which is unlikely to impact typical usage. [17] If using Kotlin, note that support for version 1.7.x was dropped in Jackson 2.18. [17, 19]

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