19 Posts getaggt mit "2024.2"

Two vulnerabilities CVE-2026-24734 and CVE-2025-66614 have been disclosed, affecting the Tomcat Web Application Server.

A version of Tomcat is included in the INFOMOTION Data Management Center package and used for the containerized and standalone deployment options. We are now releasing an updated version 2024.2.15 of Data Management Center that includes a patched version of Apache Tomcat.

Please note that this patch only secures containerized or standalone DMC deployments. When deployed within a custom Tomcat installation, that installation should be patched as well.

(since 2024.2.14)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.15

Bugfixes​

• Fixed a potential ConcurrentModificationException when QS rules were executed in parallel.

(since 2024.2.13)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.14

With the release of DMC version 2025.2 with long-term-support (LTS), the previous LTS version 2024.2 is reaching it's end of life.

We will continue to offer security patches until 15.03.2026 to give customers time to upgrade to the new 2025.2 LTS release.

Two vulnerabilities CVE-2025-55752 and CVE-2025-55754 have been disclosed, affecting the Tomcat Web Application Server.

A version of Tomcat is included in the INFOMOTION Data Management Center package and used for the containerized and standalone deployment options. We are now releasing an updated version 2024.2.13 of Data Management Center that includes a patched version of Apache Tomcat.

Please note that this patch only secures containerized or standalone DMC deployments. When deployed within a custom Tomcat installation, that installation should be patched as well.

(since 2024.2.12)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.13

A version of the Microsoft JDBC Driver for SQL Server is included in the INFOMOTION Data Management Center package and used across all deployment options. We are now releasing an updated version 2024.2.12 of Data Management Center that includes a patched version of the Microsoft JDBC Driver for SQL Server to address CVE-2025-59250.

Bugfixes​

• Fix: Table-UI (List of tables) did not update when a table was deleted

(since 2024.2.11)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.12

CVE-2025-41242​

A vulnerability in the Spring Framework CVE-2025-41249 has been reported. The INFOMOTION Data Management Center (DMC) includes the Spring Framework as part of its package.

Based on our analysis and existing automated tests of authorization procedures, we do not believe Data Management Center to be impacted by the vulnerability.

Nonetheless, we are now releasing an updated version 2024.2.11 of Data Management Center that includes a patched version of the Spring Framework.

Dependency Upgrades​

• Upgrade Spring Boot from 6.2.10 to 6.2.11.

Features​

• Added ENV Parameter DMC_TRIM_ALL_NON_PKS to trim all non-primary-key fields.

Bugfixes​

• Ensured proper rollback of caches when DeploymentSet import fails due to exceptions.
• Fixed incorrect validation in Trigger Form.
• Fixed incorrect validation in Task Form.
• Fixed translation error in Table-View.
• Resolved error in Admin-Task-View caused by invalid commands missing a tableId. Added a tooltip to indicate when a command is invalid and will not be scheduled.
• Improved error message for Objects not found: COMMAND #-2147483648 when deleting a command referenced by a task.
• Editing is now possible when domain values are invalid; outdated entries (not part of the list of values) are shown with a warning.
• Fixed issue where entries could not be deleted if a primary key field was set to null.
• Scheduled commands that fail due to a missing command are now automatically unscheduled.

(since 2024.2.10)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.11

CVE-2025-48989​

A vulnerability CVE-2025-48989 has been disclosed, affecting the Tomcat Web Application Server.

A version of Tomcat is included in the INFOMOTION Data Management Center package and used for the containerized and standalone deployment options. We are now releasing an updated version 2024.2.10 of Data Management Center that includes a patched version of Apache Tomcat.

Please note that this patch only secures containerized or standalone DMC deployments. When deployed within a custom Tomcat installation, that installation should be patched as well.

CVE-2025-41242​

A vulnerability CVE-2025-41242 has been disclosed, affecting certain Spring Framework MVC applications in non-compliant servlet environments.

The INFOMOTION Data Management Center (DMC) includes the Spring Framework as part of its package.
We are now releasing an updated version 2024.2.10 of Data Management Center that includes a patched version of Spring Framework.

Please note:

• Deployments of DMC using the embedded Tomcat servlet container are not affected by this vulnerability, since Tomcat properly rejects malicious path sequences.
• Nevertheless, we include the patched Spring Framework in this release to ensure ongoing security and compatibility.
• If DMC is deployed within a custom servlet container, that environment should be checked and updated accordingly.

Dependency Upgrades​

• Upgrade Tomcat from 10.1.43 to 10.1.44 to avoid potential issues with CVE-2025-48989.
• Upgrade Spring Boot from 6.2.8 to 6.2.10 to avoid potential issues with CVE-2025-41242

Bugfixes​

• Fixed an issue where List-of-Values without a filterColumn failed with cryptic errors.
• Fixed an issue where the checkmark on the update view is shows the incorrect state.
• Fixed an issue where QS rules were not revalidated when the table changes, which resulted in invalid SQLs.
• Fixed an issue where commands configured with QA CHECK BEFORE EXECUTION and Abort on error failed with a INTERNAL_SERVER_ERROR if no QA rules were defined.
• Fixed a header configuration error within table/{tableId}/data/delete.
• Prevented use of SQL keywords in columnName or title during Create-Table-Process.
• Fixed cryptic errors in the TablePerm workflow.
• Fixed a deserialization error for table permissions during the create process.
• Fixed an issue where the view did not update after importing a Deployment Set.
• Fixed an issue where attempting to rename a column during deployment-import lead to cryptic error message

Improvements​

• Enhanced Field descriptions within Input-Data fields.

(since 2024.2.9)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.10

Two separate vulnerabilities CVE-2025-53506 and CVE-2025-52520 have been disclosed, affecting the Tomcat Web Application Server.

A version of Tomcat is included in the INFOMOTION Data Management Center package and used for the containerized and standalone deployment options. We are now releasing an updated version 2024.2.9 of Data Management Center that includes a patched version of Apache Tomcat.

Please note that this patch only secures containerized or standalone DMC deployments. When deployed within a custom Tomcat installation, that installation should be patched as well.

Dependecy Upgrades​

• Upgrade to Spring Boot 3.4.8 including embedded Tomcat 10.1.43 to avoid potential issues with CVE-2025-53506 and CVE-2025-52520

(since 2024.2.8)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.9

A vulnerability CVE-2025-48988 has been disclosed, affecting the Tomcat Web Application Server:
"DoS in multipart upload"

A version of Tomcat is included in the INFOMOTION Data Management Center package and used for the containerized and standalone deployment options. We are now releasing an updated version 2024.2.8 of Data Management Center that includes a patched version of Apache Tomcat.

Please note that this patch only secures containerized or standalone DMC deployments. When deployed within a custom Tomcat installation, that Tomcat installation should be patched as well.

Dependency Upgrades​

• Upgrade to Spring Boot 3.4.7 including embedded Tomcat 10.1.42 to avoid potential issues with CVE-2025-48988

(since 2024.2.7)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.8

The Spring project has published a Security Advisory concerning Spring Framework, an open-source library used by INFOMOTION Data Management Center.

Based on our analysis and the available information, the relevant vulnerability CVE-2025-41234 does not affect INFOMOTION Data Management Center since our application does not prepare headers using org.springframework.http.ContentDisposition.

Nonetheless, we are publishing a Patch Release of Data Management Center with an updated & fixed version of Spring Framework.

Dependency Upgrades​

• Upgrade to Spring Framework from 6.2.5 to 6.2.8 to avoid potential issues with CVE-2025-41234

(since 2024.2.6)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.7

Bugfixes​

• Properly load previously defined triggers on application startup
• Execute scheduled tasks as system user to avoid permissions errors
• Fix behaviour for very-high-precision numbers on MSSQL

(since 2024.2.5)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.6

Two separate vulnerabilities CVE-2025-31650 and CVE-2025-31651 have been disclosed, affecting the Tomcat Web Application Server.

A version of Tomcat is included in the INFOMOTION Data Management Center package and used for the containerized and standalone deployment options. We are now releasing an updated version 2024.2.5 of Data Management Center that includes a patched version of Apache Tomcat.

Please note that this patch only secures containerized or standalone DMC deployments. When deployed within a custom Tomcat installation, that installation should be patched as well.

Dependecy Upgrades​

• Upgrade to Spring Boot 3.4.5 including embedded Tomcat 10.1.40 to avoid potential issues with CVE-2025-31650 and CVE-2025-31651

(since 2024.2.4)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.5

Bugfixes​

• Upgrade to Spring Boot 3.4.4 including embedded Tomcat 10.1.39 to avoid potential issues with CVE-2025-24813

(since 2024.2.3)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.4

A vulnerability CVE-2025-24813 has been disclosed, affecting the Tomcat Web Application Server.

A version of Tomcat it is included in the INFOMOTION Data Management Center package and used for the containerized and standalone deployment options.

While the vulnerability is flagged as potentially having a critical impact, the published information lists very specific preconditions. Based on our understanding, the information disclosure and remote code execution scenarios depend (among others) on the following preconditions being met:

• The Tomcat default servlet must be enabled
• Additionally, it must be configured enable writes

Both of these are not given in the INFOMOTION Data Management Center:

• The Tomcat Default Servlet is not enabled within DMC.
• Also, the servlet is read-only by default unless explicitly configured otherwise, which DMC does not do.

Nonetheless, we will be releasing an updated version 2024.2.4 of Data Management Center shortly that includes a patched version of Apache Tomcat.

Please note that this patch only secures containerized or standalone DMC deployments. When deployed within a custom Tomcat installation, that installation should be patched as well.

Bugfixes​

• Allow users to choose .xlsm files for upload

• Use base image containing shell & mkdir for DMC container build

(since 2024.2.2)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.3

Bugfixes​

• Properly report all columns if multiple required columns are missing

(since 2024.2.1)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.2

Bugfixes​

• Avoid error message when uploading files with duplicate (case-insensitive) column name
• Fix error when displaying all QS violations with QS rules containing placeholders
• Container Image only: Update included Java Runtime Environment (JRE) to 17.0.14 fixing CVE-2025-21502

(since 2024.2.0)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.1

Oracle has published a Security Advisories for Java as part of it's Januar 2025 Critical Patch Update Advisory that is relevant for INFOMOTION Data Management center under certain conditions:

• Generally speaking, Java is not part of DMC itself, which is therefore not directly affected.
• However, the pre-built container images we distribute since Release 2024.1 contain a Java Runtime Environment (Java version 17).

CVE-2025-21502 has been classified by Oracle as a low-impact and high-complexity attack on Java versions up to 17.0.13. Unfortunately, there is not enough information available yet to be able to asses if and how INFOMOTION Data Management Center might be affected by the issue in the underlying JRE.

As a precaution we are releasing an updated DMC version 2024.2.1.

In addition to two bugfixes (see release notes), the container images published for this patch update the JRE to version 17.0.14 which, according to the published information, is not affected by either CVE.

If you have further questions, please create a DMC support ticket via eMail.

Bugfixes​

• Proper validation of empty primary keys during file import
• Fix rare frontend error when editing table properties with empty description
• Revert paginator to show row numbers instead of page numbers
• Avoid potential deadlocks when deleting many cached objects at once...
• Avoid various (transient) error messages when deleting many tables at once
• Remove swagger-ui due to CVE-2024-45801
• Apply default column mappings case-insensitive
• Fix an error occurring when sorting by hist_from in specific cases for MSSQL database
• Fix permissions check when editing table/data permissions
• Increase maximum number of decimal digits when using embedded H2 database

Improvements​

• Allow copying table columns
• Ensure usernames are only logged at DEBUG or TRACE level
• Built-in database ("db") authentication disabled by default
• Frontend improvements for long-running operations (delete multiple tables, import deployment set)
• Additional logging for file imports
• Allow at least partial startup & debug output when configuration is missing
• Allow removal of the last filter

(since 2024.1.6)

Docker-Image: infomotiondmc.azurecr.io/dmc:2024.2.0