Release 1.11.1
Release Date: 03/11/2023
Features
-
External document validation now detects
lock actions
, namelylock
signatures. -
Allow developers to add custom hibernate parameters to eSign datasource configurations.
-
Added friendly names to each datasource connection pool, allowing better troubleshooting when using monitoring tools or JMX directly.
-
New Analytics API method to retrieve metainfo about analytics configurations.
Fixes
-
Added ability to recover from temporary unavailability in Multicert services, when used for signing with qualified certificates.
-
Fixed issue introduced in 1.11.0 that prevent non-signature form fields from being rendered in eSign Viewer.
-
Fixed issue occurring when "server.viewer.ie11.force" is set to
true
. Each caused a redirect with HTTP instead of HTTPS. -
Fixed security vulnerabilities.
Security Vulnerabilities
Whitelisted vulnerabilities
Dependency | Vulnerability | Description |
---|---|---|
bcprov-jdk15on |
CVE-2023-33201 |
This vulnerability only affects integrations with LDAP CertStore, which is out of the scope of eSign |
h2 |
CVE-2022-45868 |
These vulnerabilities only affect H2 databases, which are intended for demo purposes only and should not be used in production environments |
itext-core |
CVE-2022-24198 |
iText dismissed this CVE: "Vendor does not view this as a vulnerability and has not found it to be exploitable." |
jackson-databind |
CVE-2023-35116 |
"The vendor’s perspective is that the product is not intended for use with untrusted input." |
jose4j |
CVE-2023-31582 |
This vulnerability does not affect eSign as it does not allow the configuration of the number of hashing iterations (which is set at a safe level). |
quartz |
CVE-2023-39017 |
Quartz functionalities are not exposed to the outside. |
spring-web |
CVE-2016-1000027 |
Spring dismissed this CVE: "The vendor’s position is that untrusted data is not an intended use case. The product’s behavior will not be changed because some users rely on deserialization of trusted data." |
Upgrade Notes
If upgrading from 1.10.x, check the migration steps to understand how to upgrade.