[Snyk] Fix for 1 vulnerabilities

[chrislin22]

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	710	org.opensearch.client:opensearch-rest-high-level-client: 2.16.0 -> 2.19.6 No Path Found Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

Vulnerabilities that could not be fixed

• Upgrade:
  • Could not upgrade com.fasterxml.jackson.core:jackson-databind@2.16.0 to com.fasterxml.jackson.core:jackson-databind@2.18.8; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/com/fasterxml/jackson/jackson-bom/2.16.0/jackson-bom-2.16.0.pom

---

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

[chrislin22]

Summary of Upgrades

This update involves minor version bumps for jackson-databind and opensearch-rest-high-level-client. The primary risk is associated with the OpenSearch client upgrade, which introduces a change in the default k-NN engine that could affect vector search behavior.

com.fasterxml.jackson.core:jackson-databind 2.16.0 → 2.18.8

Risk: Low

This is a minor version upgrade. The changes between 2.16.0 and 2.18.8 primarily consist of bug fixes, performance improvements, and new additive features. Key changes include:

• New Features: A new DeserializationFeature.FAIL_ON_UNEXPECTED_VIEW_PROPERTIES was added in 2.17 to enforce stricter view-based deserialization. Version 2.18 introduced a major rewrite of the property introspection logic for better handling of annotations and creator properties.
• Behavioral Changes: There are no significant documented breaking changes for standard usage. However, the property introspection rewrite in 2.18, while intended to fix bugs, could subtly alter behavior in complex use cases, particularly those involving custom creators or annotations.
• Kotlin Module: For Kotlin users, version 2.18 removes support for Kotlin 1.7 and removes previously deprecated constructors and accessors in KotlinModule.Builder.

Recommendation: While the risk is low, projects with complex Jackson customizations or heavy reliance on Kotlin data classes should perform regression testing.

org.opensearch.client:opensearch-rest-high-level-client 2.16.0 → 2.19.6

Risk: Medium

This upgrade spans several minor versions and introduces a notable behavioral change and deprecation notices.

• Behavioral Change (k-NN): Version 2.18.0 changed the default k-NN engine from NMSLIB to Faiss. If you use the cosinesimil space type without explicitly defining an engine, Faiss will now be used. Faiss normalizes vectors to unit length for cosine similarity, which means stored vector values will differ from the input values. This could impact applications that retrieve and use these stored vectors.
• Deprecation Notices: Version 2.19.0 announced the future deprecation of support for Ubuntu 20.04 and Amazon Linux 2 for OpenSearch Dashboards.
• New Features: The releases include numerous new features, such as disk-optimized vector search (2.17), performance improvements for vector search (2.18), and new query insights dashboards (2.19).

Recommendation: The change in the default k-NN engine presents a medium risk. It is critical to verify the behavior of any k-NN vector search functionality, especially if you rely on cosine similarity with the default engine. If your application retrieves vectors post-indexing, you must validate that the normalized vectors do not break your logic.

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