[Snyk] Fix for 2 vulnerabilities

[macroscope-cloud]

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

Snyk changed the following file(s):

• examples/iOS-Hybrid-App-Java-Server/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Improper Authentication SNYK-JAVA-ORGAPACHETOMCATEMBED-17732890	726	org.apache.tomcat.embed:tomcat-embed-core: 11.0.10 -> 11.0.23 org.apache.tomcat.embed:tomcat-embed-websocket: 11.0.10 -> 11.0.23 No Known Exploit
	Detection of Error Condition Without Action SNYK-JAVA-ORGAPACHETOMCATEMBED-17733746	721	org.apache.tomcat.embed:tomcat-embed-core: 11.0.10 -> 11.0.23 org.apache.tomcat.embed:tomcat-embed-websocket: 11.0.10 -> 11.0.23 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:

🦉 Improper Authentication

[macroscope-cloud]

This is a minor version upgrade for Apache Tomcat, which primarily includes bug fixes, security patches, and dependency updates. No major API removals or mandatory code changes are documented in this range.

However, the risk is assessed as medium due to a specific breaking change introduced in version 11.0.23:

• Clustering EncryptInterceptor: A breaking change was made to the EncryptInterceptor used in clustering configurations. Migrating to 11.0.23 requires that all nodes in the cluster are stopped and restarted to handle the change. [11]

Recommendation:
If you are using Tomcat's clustering feature with the EncryptInterceptor, you must plan for a coordinated restart of all cluster nodes during deployment. If you are not using this specific feature, the upgrade is likely to be low risk, consisting of beneficial bug and security fixes. [2]

Source: Apache Tomcat 11 Migration Guide, Tomcat 11 Changelog

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