Versions Compared

Old Version 1

changes.mady.by.user Geert Graat

Saved on

compared with

New Version Current

changes.mady.by.user Geert Graat

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Identifier

Component

Issue

Solution

BQ-14474

 


CVE-2021-43797 & CVE-2021-23463 are reported on the runtime

CVE-2021-43797 concerns a Netty library which was updated to the latest version in which the CVE is resolved. CVE-2021-23463 concerns H2, which we only ship with the development-tools component. This component is meant to be used for development and not for production. H2 can also be used as a database backend, but this is strongly discouraged in production environments. So we have not updated the H2 library as production is unaffected

.

BQ-14460

 

CVE-2021-44228 was reported on the log4j-core package.

Blueriq doesn't use log4j-core as a dependency, nor does it ship this package. To be totally sure, however, we upgraded the versions of the log4j related packages that we do use (log4j-api and log4j-to-slf4j) to version 2.15.0

.

For more information, see [this statement from Blueriq

CSD-3970

JAVA Runtime

When importing a profile.xml using the XmlConverter an exception is thrown when loading an already existing singleton entity instance.

This was a regression which occurred after the resolution of CSD-3923. When importing a profile.xml into a prefilled profile the existing singletons will be used, otherwise the imported profile instance will be used.

CSD-3912

 


The inability to find a qualified name when importing a WSDL would omit the qualified name, making it hard to debug the issue.

The qualified name that could not be found is now included in the log.

CSD-3931

 


Importing a branch export from a Studio version older than R13 could fail if it contains external libraries that require a migration.

When an older branch export is imported into a newer Studio version, any external libraries are now correctly migrated as well.

CSD-3930

 


When an inline field is present on a page, the generation of a document using the document plugin would fail

Inline fields no longer cause the document generation plugin to fail