[Snyk] Fix for 3 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• debezium-server/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-IONETTY-18233079	170	software.amazon.awssdk:kinesis: 2.13.13 -> 2.49.1 Major version upgrade No Path Found Proof of Concept
	Infinite loop SNYK-JAVA-IONETTY-18230935	125	software.amazon.awssdk:kinesis: 2.13.13 -> 2.49.1 Major version upgrade No Path Found No Known Exploit
	Incorrect Implementation of Authentication Algorithm SNYK-JAVA-ORGECLIPSEJETTY-18230938	125	No Path Found No Known Exploit

Breaking Change Risk

Notice: This assessment is enhanced by AI.

Vulnerabilities that could not be fixed

• Upgrade:
  • Could not upgrade io.debezium:debezium-embedded@1.2.0-SNAPSHOT to io.debezium:debezium-embedded@3.3.0.Final; Reason could not apply upgrade, dependency is managed externally ; Location: provenance does not contain location
• Could not upgrade io.quarkus:quarkus-smallrye-health@1.4.1.Final to io.quarkus:quarkus-smallrye-health@2.3.0.Final; Reason could not apply upgrade, dependency is managed externally ; Location: provenance does not contain location

---

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

[snyk-io]

This upgrade includes multiple major version jumps with significant breaking changes, requiring environment and code modifications.

Top 3 Most Impactful Upgrades:

• io.debezium:debezium-embedded 1.2.0-SNAPSHOT → 3.3.0.Final (HIGH)
  This is a very large version jump across two major versions (1.x → 2.x → 3.x) and requires significant migration effort. Key breaking changes include:

  • Java Runtime Upgrade: Debezium 2.x requires Java 11, and Debezium 3.x requires Java 17.
  • Configuration Properties: Many configuration properties have been renamed. For example, database.server.name is now topic.prefix, and database.history.* properties are now prefixed with schema.history.internal.*.
  • Event Structure: The structure of the change data capture events has been modified, for example by adding a before field to the record content.
  • Default Behavior: Default values for properties like schema.name.adjustment.mode and SSL settings have changed, which could alter connector behavior.
  • Recommendation: A staged migration is critical. Plan for a Java 17 runtime. Carefully review the Debezium 2.0 and 3.0 release notes to map all old configuration properties to their new equivalents and adapt your code to handle the new event structure.

• io.quarkus:quarkus-smallrye-health 1.4.1.Final → 2.3.0.Final (HIGH)
  This upgrade crosses the Quarkus 1.x to 2.x major version boundary, which introduces several platform-level breaking changes.

  • Java 11 Required: Quarkus 2.0 requires a minimum of JDK 11, dropping support for JDK 8.
  • Build Tooling: The minimum required Apache Maven version was raised to 3.8.1.
  • Configuration & Behavior: Changes were made to how JSON is configured via Vert.x, how CDI lifecycle methods (@PostConstruct) are intercepted, and how multi-module projects are indexed.
  • Recommendation: Your environment must use at least JDK 11. Review the Quarkus 2.0 migration guide to check for deprecated properties and behavioral changes in CDI and other extensions that could affect your application.

• software.amazon.awssdk:kinesis 2.13.13 → 2.49.1 (LOW)
  While this is a wide version range, it occurs within the same major version (v2) of the AWS SDK for Java. The SDK maintains strong backward compatibility within a major version.

  • The updates primarily consist of additive features, performance improvements, and bug fixes. No breaking API changes for the Kinesis client are documented in

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

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.