MarkLogic Data Hub 6.2 - Release Notes

Data Hub 6.2.0

Data Hub 6.2.0 includes the following new features and changes:

Smart Collector Enhancements

Features

Non-Reprocessing of Documents: The Smart Collector prevents the reprocessing of documents that have already been processed. This enhancement optimizes performance and ensures the efficient use of resources by avoiding duplicate processing.

External Schema Integration

Features

Support for External Schemas: The Data Hub Entity features have been upgraded to work seamlessly with schemas that are defined externally. This includes support for:

  1. JSON Schema
  2. XML Schema
  3. Semaphore Modeling

This integration creates greater flexibility and interoperability, enabling users to define their data structures externally while still leveraging the powerful capabilities of Data Hub.

Other Updates

Various dependencies address third-party vulnerabilities.

Security Notice

The Data Hub Central 6.2.0 war file depends on the 5.3.39 version of the Spring Core libraries. These dependencies contain known vulnerabilities, but you can remove the known attack vectors as distributed.

These attack vectors could potentially be opened up by misconfiguration in the Hub Central environment. To avoid misconfiguration, see below.

Use a Hardened Web Application Server

Features
NVD - CVE-2024-38816

“[M]alicious requests are blocked and rejected when any of the following is true:

  1. the Spring Security HTTP Firewall HttpFirewall :: Spring Security is in use
  2. the application runs on Tomcat or Jetty"

Use an ANT Pattern Matching Strategy

Features
NVD - CVE-2023-44794

“An issue in Dromara SaToken version 1.36.0 and before allows a remote attacker to escalate privileges via a crafted payload to the URL."

The default application.properties shipped in the Hub Central war file contains the following entry: spring.mvc.pathmatch.matching-strategy=ant_path_matcher as the proposed workaround.

Do not override this value. (Source: SaToken and Spring's differential handling of URIs raises authorization bypass vulnerabilities

Do Not Use HttpInvokerServiceExporter

Release Notes for Earlier Versions