[Snyk] Fix for 3 vulnerabilities

[chrislin22]

Snyk has created this PR to fix 3 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
	Improper Certificate Validation SNYK-JAVA-ORGBOUNCYCASTLE-18512789	751	org.bouncycastle:bc-fips: 1.0.2 -> 1.0.2.7 No Known Exploit
	Improper Validation of Integrity Check Value SNYK-JAVA-ORGBOUNCYCASTLE-18512975	721	org.bouncycastle:bcpkix-fips: 1.0.2 -> 1.0.12 No Known Exploit
	Improper Verification of Cryptographic Signature SNYK-JAVA-ORGBOUNCYCASTLE-18513029	721	org.bouncycastle:bcpkix-fips: 1.0.2 -> 1.0.12 No Known Exploit

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.

[chrislin22]

This is a low-risk upgrade involving patch and minor version increments for Bouncy Castle's FIPS-certified libraries. These updates are within the same major version series and are expected to be backward compatible, primarily delivering security fixes and bug patches.

• org.bouncycastle:bc-fips (1.0.2 → 1.0.2.7): This is a patch update. For FIPS-certified modules, patch releases are designed to address security vulnerabilities and bugs without altering the core cryptographic functions or breaking API compatibility.

• org.bouncycastle:bcpkix-fips (1.0.2 → 1.0.12): This is a minor version update for the PKIX API layer. While specific release notes for this range are not readily available, changes within the 1.0.x series are generally backward-compatible. Significant breaking changes were introduced in the 2.x series, which is not part of this upgrade.

No breaking changes are documented for these specific version ranges. The risk is considered low as these updates should be safe to apply without requiring code modifications.

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