Release History for Solace MicroIntegration for SFTP, Version 1.5.1
May 2026
This section lists the new features introduced in the Solace MicroIntegration for SFTP for
release 1.5.1 and earlier releases.
| Name | Description | Introduced in Version |
|---|---|---|
| Add support for XML samples to the transformation feature |
You can now use XML payloads in addition to JSON payloads when you create data mappings in Micro-Integration Flows. This enhancement allows you to work with data from legacy systems that use XML formats and transform it for use with modern systems, or vice versa. When you import a payload sample, you can now upload either a well-formed JSON file or a well-formed XML file. You can then map payload fields and apply transformation functions to modify the data as it flows through your Micro-Integration. This feature supports XML-to-XML, XML-to-JSON, and JSON-to-XML transformations, giving you the flexibility to repurpose your events by choosing different content types for your source and target systems. |
1.4.0 |
| New functions for MI transformations: base64 encode and decode | self and cloud managed |
Added transformation functions for Base64 encoding and decoding with support for Standard, URL-safe, and MIME variants.
|
1.3.1 |
| Spring Cloud Stream binder performance improvements to MIs |
Performance improvements through architectural optimizations in message processing. These enhancements enable substantially higher message throughput and more efficient resource utilization, allowing for handling of larger workloads with the same infrastructure. In addition, further optimizations were done by enabling asynchronous publishing by default on Micro Integrations that support it, and disabling the default internal back-pressure for faster asynchronous publishing. |
1.2.1 |
| Connector Framework - per message payload identification and field-level transformations |
A new configuration section and capabilities around transforming source headers and payload to desired mappings on the target headers and payload has been added. The mappings are expressed in the connector configuration using an expression language based on Spring Expression Language (SpEL).
This release supports JSON payloads only. Future releases will add other content formats such as XML. If your source and target payload is not JSON, you cannot map or transform the payload and it is passed through as is. However, you can still do header transforms and smart topic dynamic producer destinations. This is a new capability and is not compatible with the "transform-headers" and "transform-payload" sections of the configuration available prior to this release. The "transform-headers" and "transform-payload" sections continue to work but are now deprecated and will be removed in a future release. Existing connector configurations that rely on the legacy transform sections should not use the new transform capabilities. The legacy and new transform sections cannot be used together. |
1.1.0 |
| SCSt binder: Add support for NACK |
Added support (internal) for NACK handling of messages not processed due to error. This is a breaking change regarding supported PubSub+ broker versions. The connectors now require a 10.2.1+ broker version to operate.
|
1.0.0 |
| SFTP Micro-Integration |
The initial release of the SFTP Micro-Integration, which enables seamless bidirectional data flow between SFTP servers and Solace. It lets you read files from SFTP, process and split their contents, then publish the data to Solace. Similarly, you can also write Solace events back to SFTP servers. For more details, check out the full documentation.
|
1.0.0 |
This section lists the history of resolved issues in the Solace MicroIntegration for SFTP for
release 1.5.1 and earlier releases.
| Reference Number | Description | Resolved in Version |
|---|---|---|
| DATAGO-121267 |
As a result of an asynchronous publish failure, when negatively acknowledging the corresponding consumed message from Solace, queue retries were not respected. Similarly, when consuming from a non-Solace source, then negative acknowledgements to that source may potentially fail.
|
1.2.1 |
| DATAGO-105471 |
Added destination header in Solace Source micro-integrations SMF metadata
|
1.1.13 |
| DATAGO-67217 |
Added sanitizing of message payload and header values (header names remain visible) in Error logs from messaging exceptions. Potentially sensitive values will now appear as ******.
|
1.0.0 |
| DATAGO-71588 |
You may see a discrepancy where the container's health status is reported as unhealthy despite the health endpoint confirming a status of "UP".
|
1.0.0 |
| DATAGO-71738 |
StreamMessages are not supported by this version of the connector due to an issue within the Spring Framework. Solace is working with Spring to address this issue and will reinstate StreamMessage support in a future release. Attempted processing of StreamMessages will result in an “UnsupportedOperationException” in the connector.
|
1.0.0 |
| DATAGO-69335 |
Fixed the issue in reading user property having value of type byte[] or ByteArray while mapping Solace Consumer message to Spring message.
|
1.0.0 |
This section lists the history of changed functionality in the Solace MicroIntegration for SFTP
for release 1.5.1 and earlier releases.
| Reference Number | Description | Introduced in Version |
|---|---|---|
| DATAGO-133191 |
Upgrade connector to Spring Boot 3.5.14
|
1.5.1 |
| DATAGO-132479 |
Upgrade connector base image to Eclipse Temurin 17.0.18_8-jre-alpine-3.23 (sha256:88c0002860cda56384d5ed3b2da4d0d9a2b44dc2ee4dc02344be985bd8b524bc)
|
1.5.1 |
| DATAGO-130790 |
Upgrade connector to Spring Cloud 2025.0.2
|
1.5.0 |
| DATAGO-130061 |
Upgrade connector to Spring Boot 3.5.13
|
1.5.0 |
| DATAGO-130215 |
Upgrade connector to JCSMP 10.28.3
|
1.5.0 |
| DATAGO-128563 |
Upgrade Spring Boot Admin to 3.5.8
|
1.5.0 |
| DATAGO-128439 |
Add support for Prometheus Monitoring tooling for observability.
|
1.5.0 |
| DATAGO-125812 |
Upgrade connector to Spring Boot 3.5.11
|
1.4.0 |
| DATAGO-124658 |
Upgrade connector to Spring Boot Admin 3.5.7
|
1.3.1 |
| DATAGO-120869 |
Upgrade connector to Spring Boot 3.5.10
|
1.3.1 |
| DATAGO-124644 |
Upgrade connector base image to Eclipse Temurin 17.0.18_8-jre-alpine (sha256:7aa804a1824d18d06c68598fe1c2953b5b203823731be7b9298bb3e0f1920b0d).
|
1.3.1 |
| DATAGO-108854 |
Enable the workflow’s asynchronous publishing configuration option by default for improved performance. The workflow’s acknowledgment.publish-async property now defaults to true.
|
1.2.1 |
| DATAGO-118041 |
Upgrade connector to Spring Boot 3.5.8
|
1.2.1 |
| DATAGO-119789 |
Upgrade connector to Netty 4.1.128.Final
|
1.2.1 |
| DATAGO-120873 |
Upgrade connector to Spring Cloud 2025.0.1
|
1.2.1 |
| DATAGO-117314 |
Upgrade connector to Eclipse Temurin 17.0.17_10-jre-alpine (sha256:f57e47e7a78ae1ff5019681d95a4964153b0d1078bdff2a2f288e4a5ee329c14)
|
1.2.1 |
| DATAGO-114547 |
Added startup notice/banner regarding upcoming executable artifact renaming. Users should prepare to update automation scripts when this change takes effect in a future release.
|
1.2.1 |
| DATAGO-116367 |
Upgrade connector to Solace JCSMP 10.28.2
|
1.1.26 |
| DATAGO-116368 |
Upgrade connector to Spring Boot Admin 3.5.6
|
1.1.26 |
| DATAGO-116369 |
Upgrade connector to Spring Boot 3.5.7
|
1.1.26 |
| DATAGO-111022 |
Upgrade connector to Solace Spring Cloud 4.10.0
|
1.1.23 |
| DATAGO-112062 |
Upgrade connector to Spring Boot 3.5.6 and Spring Cloud 2025.0.0
|
1.1.23 |
| DATAGO-112077 |
Upgrade connector to Spring Boot Admin 3.5.5
|
1.1.23 |
| DATAGO-109647 |
Upgrade connector to Spring Boot 3.4.9
|
1.1.20 |
| DATAGO-110219 |
Upgrade connector to Solace JCSMP 10.28.1
|
1.1.20 |
| DATAGO-108538 |
Upgrade connector to Solace Spring Cloud 4.8.1
|
1.1.20 |
| DATAGO-109668 |
Disable the workflow’s back-pressure by default for improved performance. The workflow’s acknowledgment.back-pressure-threshold property now defaults to -1 (disabled). For flow control, consider using native client back-pressure mechanisms instead.
|
1.1.20 |
| DATAGO-107408 |
Upgrade connector to JCSMP 10.27.3
|
1.1.16 |
| DATAGO-107134 |
Upgrade connector to Spring Boot Admin 3.4.7
|
1.1.16 |
| DATAGO-108120 |
Upgrade connector base image to Eclipse Temurin 17.0.16_8-jre-alpine (sha256:fc47f4a190b599de0835d98830976f5938588b4c17b07f19dba903d5b29f666e).
|
1.1.16 |
| DATAGO-107376 |
Upgrade connector to Spring Boot 3.4.8
|
1.1.16 |
| DATAGO-106868 |
Upgrade connector to Spring Cloud 2024.0.2
|
1.1.16 |
| DATAGO-104715 |
Upgrade connector to Spring Boot 3.4.7
|
1.1.13 |
| DATAGO-104989 |
Deprecate maskNumber() function in transformation capabilities
|
1.1.13 |
| DATAGO-104294 |
Upgrade connector to JCSMP 10.27.2
|
1.1.13 |
| DATAGO-105065 |
Upgrade SFTP connector to spring-cloud-stream-binder-camel 1.4.4
|
1.1.13 |
| DATAGO-102718 |
Upgrade connector to Spring Boot Admin 3.4.6
|
1.1.9 |
| DATAGO-102716 |
Upgrade connector to JCSMP 10.27.1
|
1.1.9 |
| DATAGO-102715 |
Upgrade connector to Spring Boot 3.4.6
|
1.1.9 |
| DATAGO-99526 |
Upgrade connector to Solace Spring Cloud 4.8.0
|
1.1.6 |
| DATAGO-99525 |
Upgrade connector to JCSMP 10.27.0
|
1.1.6 |
| DATAGO-99793 |
Upgrade connector base image to Eclipse Temurin 17.0.15_6-jre-alpine (sha256:b10e4fda9d71b3819a91fbb0dbb28512edbb37a45f6af2a301c780223bb42fb8).
|
1.1.6 |
| DATAGO-99796 |
Upgrade connector to Spring Boot 3.4.5
|
1.1.6 |
| DATAGO-97529 |
Upgrade connector to Spring Boot 3.4.4
|
1.1.3 |
| DATAGO-97477 |
Upgrade connector to Spring Cloud 2024.0.1
|
1.1.3 |
| DATAGO-97166 |
Upgrade connector to JCSMP 10.26.0
|
1.1.3 |
| DATAGO-97063 |
Upgrade connector to Spring Boot Admin 3.4.5
|
1.1.3 |
| DATAGO-95501 |
Upgrade connector base image to Eclipse Temurin 17.0.14_7-jre-alpine (sha256:865cca6d0b31f284a5fc4e8cbd8f9375f470fd07cf6e909cea62f2790d4187fe).
|
1.1.0 |
| DATAGO-95206 |
Upgrade connector to Spring Boot Admin 3.4.2
|
1.1.0 |
| DATAGO-95698 |
Upgrade connector to Spring Boot 3.4.3
|
1.1.0 |
| DATAGO-92892 |
Upgrade connector to Camel Spring 4.9.0
|
1.0.2 |
| DATAGO-93240 |
Upgrade connector to Spring Boot 3.4.2
|
1.0.2 |
| DATAGO-93224 |
Upgrade connector base image to Eclipse Temurin 17.0.13_11-jre-alpine (sha256:8164ba7f332faf27462e055013c2aa518a2eba1ce6984e9ca60dadb899cab6bd).
|
1.0.2 |
| DATAGO-93220 |
Upgrade connector to Solace Spring Cloud 4.7.0
|
1.0.2 |
| DATAGO-92283 |
Upgrade connector base image to Eclipse Temurin 17.0.13_11-jre-alpine (sha256:04ea31625d7771f3272bdc533a2871c00a8268f1a6774528b2a7389515f7b5b1).
|
1.0.0 |
| DATAGO-89778 |
Upgrade connector to Spring Boot 3.4.1 and Spring Cloud 2024.0.0
|
1.0.0 |
| DATAGO-92733 |
Upgrade connector to JCSMP 10.25.2
|
1.0.0 |
The following vulnerabilities have been resolved in the Solace MicroIntegration for SFTP for
release 1.5.1 and earlier releases.
| Resolved in Version | Severity (CVSS v3 Score) | Vulnerability ID | Solace Reference Number | Affected Products | Description |
|---|---|---|---|---|---|
| 1.5.0 | CVSS v3: 8.7 (HIGH) | DATAGO-126998 | JAR |
### Summary The non-blocking (async) JSON parser in `jackson-core` bypasses the `maxNumberLength` constraint (default: 1000 characters) defined in `StreamReadConstraints`. This allows an attacker to send JSON with arbitrarily long numbers through the async parser API, leading to excessive memory allocation and potential CPU exhaustion, resulting in a Denial of Service (DoS). The standard synchronous parser correctly enforces this limit, but the async parser fails to do so, creating an inconsistent enforcement policy. ### Details The root cause is that the async parsing path in `NonBlockingUtf8JsonParserBase` (and related classes) does not call the methods responsible for number length validation. - The number parsing methods (e.g., `_finishNumberIntegralPart`) accumulate digits into the `TextBuffer` without any length checks. - After parsing, they call `_valueComplete()`, which finalizes the token but does *not* call `resetInt()` or `resetFloat()`. - The `resetInt()`/`resetFloat()` methods in `ParserBase` are where the `validateIntegerLength()` and `validateFPLength()` checks are performed. - Because this validation step is skipped, the `maxNumberLength` constraint is never enforced in the async code path. ### PoC The following JUnit 5 test demonstrates the vulnerability. It shows that the async parser accepts a 5,000-digit number, whereas the limit should be 1,000. ```j
|
|
| 1.4.0 | CVSS v3: 7.5 (HIGH) | DATAGO-125854 | JAR |
Improper Input Validation vulnerability in Apache Tomcat Native, Apache Tomcat. When using an OCSP responder, Tomcat Native (and Tomcat's FFM port of the Tomcat Native code) did not complete verification or freshness checks on the OCSP response which could allow certificate revocation to be bypassed. This issue affects Apache Tomcat Native: from 1.3.0 through 1.3.4, from 2.0.0 through 2.0.11; Apache Tomcat: from 11.0.0-M1 through 11.0.17, from 10.1.0-M7 through 10.1.51, from 9.0.83 through 9.0.114. The following versions were EOL at the time the CVE was created but are known to be affected: from 1.1.23 through 1.1.34, from 1.2.0 through 1.2.39. Older EOL versions are not affected. Apache Tomcat Native users are recommended to upgrade to versions 1.3.5 or later or 2.0.12 or later, which fix the issue. Apache Tomcat users are recommended to upgrade to versions 11.0.18 or later, 10.1.52 or later or 9.0.115 or later which fix the issue..
|
|
| 1.3.1 | CVSS v3: 7.8 (HIGH) | DATAGO-122787 | JAR |
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions png_write_image_16bit and png_write_image_8bit causes heap buffer over-read when the caller provides a negative row stride (for bottom-up image layouts) or a stride exceeding 65535 bytes. The bug was introduced in libpng 1.6.26 (October 2016) by casts added to silence compiler warnings on 16-bit systems. This vulnerability is fixed in 1.6.54.
|
|
| 1.3.1 | CVSS v3: 8.2 (HIGH) | DATAGO-109708 | JAR |
A flaw was found in GnuTLS. A double-free vulnerability exists in GnuTLS due to incorrect ownership handling in the export logic of Subject Alternative Name (SAN) entries containing an otherName. If the type-id OID is invalid or malformed, GnuTLS will call asn1_delete_structure() on an ASN.1 node it does not own, leading to a double-free condition when the parent function or caller later attempts to free the same structure. This vulnerability can be triggered using only public GnuTLS APIs and may result in denial of service or memory corruption, depending on allocator behavior.
|
|
| 1.3.1 | CVSS v3: 6.5 | netty-codec-http-4.1.128.Final.jar | DATAGO-123652 | JAR |
Netty is an asynchronous, event-driven network application framework. In versions prior to 4.1.129.Final and 4.2.8.Final, the "io.netty.handler.codec.http.HttpRequestEncoder" has a CRLF injection with the request URI when constructing a request. This leads to request smuggling when "HttpRequestEncoder" is used without proper sanitization of the URI. Any application / framework using "HttpRequestEncoder" can be subject to be abused to perform request smuggling using CRLF injection. Versions 4.1.129.Final and 4.2.8.Final fix the issue.
|
| 1.3.1 | CVSS v3: 6.9 | logback-core-1.5.18.jar | DATAGO-116834 | JAR |
ACE vulnerability in conditional configuration file processing by QOS.CH logback-core up to and including version 1.5.18 in Java applications, allows an attacker to execute arbitrary code by compromising an existing logback configuration file or by injecting an environment variable before program execution.
|
| 1.3.1 | CVSS v3: 5.3 (MEDIUM) | DATAGO-123188 | Image |
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data. Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service. The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash. Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
|
|
| 1.3.1 | CVSS v3: 9.8 (CRITICAL) | DATAGO-123188 | Image |
Issue summary: Parsing CMS AuthEnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs. Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue. OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.
|
|
| 1.3.1 | CVSS v3: 6.1 (MEDIUM) | DATAGO-123751 | JAR |
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Ja
|
|
| 1.3.1 | CVSS v3: 7.4 (HIGH) | DATAGO-123751 | JAR |
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: AWT, JavaFX). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and
|
|
| 1.2.1 | CVSS v3: 5.3 | tomcat-embed-core-10.1.46.jar | DATAGO-116515 | JAR |
Improper Resource Shutdown or Release vulnerability in Apache Tomcat.
|
| 1.2.1 | CVSS v3: 6.5 (MEDIUM) | DATAGO-120097 | JAR |
Netty is an asynchronous, event-driven network application framework. In versions prior to 4.1.129.Final and 4.2.8.Final, the `io.netty.handler.codec.http.HttpRequestEncoder` has a CRLF injection with the request URI when constructing a request. This leads to request smuggling when `HttpRequestEncoder` is used without proper sanitization of the URI. Any application / framework using `HttpRequestEncoder` can be subject to be abused to perform request smuggling using CRLF injection. Versions 4.1.129.Final and 4.2.8.Final fix the issue.
|
|
| 1.1.26 | CVSS v3: 5.3 | tomcat-embed-core-10.1.46.jar | DATAGO-116515 | JAR |
Improper Resource Shutdown or Release vulnerability in Apache Tomcat.
|
| 1.1.26 | CVSS v3: 6.9 | logback-core-1.5.18.jar | DATAGO-116525 | JAR |
ACE vulnerability in conditional configuration file processing by QOS.CH logback-core up to and including version 1.5.18 in Java applications, allows an attacker to execute arbitrary code by compromising an existing logback configuration file or by injecting an environment variable before program execution.
|
| 1.1.23 | CVSS v3: 5.8 | nimbus-jose-jwt-9.37.3.jar | DATAGO-106713 | JAR |
Connect2id Nimbus JOSE + JWT before 10.0.2 allows a remote attacker to cause a denial of service via a deeply nested JSON object supplied in a JWT claim set, because of uncontrolled recursion. NOTE: this is independent of the Gson 2.11.0 issue because the Connect2id product could have checked the JSON object nesting depth, regardless of what limits (if any) were imposed by Gson.
|
| 1.1.23 | CVSS v3: 7.5 | spring-core-6.2.10.jar | DATAGO-111876 | JAR |
The Spring Framework annotation detection mechanism may not correctly resolve annotations on methods within type hierarchies with a parameterized super type with unbounded generics. This can be an issue if such annotations are used for authorization decisions.
|
| 1.1.23 | CVSS v3: 7.5 | spring-security-core-6.5.3.jar | DATAGO-111875 | JAR |
Spring Security authorization bypass for method security annotations on parameterized types
|
| 1.1.23 | CVSS v3: 7.5 | netty-codec-4.1.124.Final.jar | DATAGO-110853 | JAR |
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In netty-codec-compression versions 4.1.124.Final and below, and netty-codec versions 4.2.4.Final and below, when supplied with specially crafted input, BrotliDecoder and certain other decompression decoders will allocate a large number of reachable byte buffers, which can lead to denial of service. BrotliDecoder.decompress has no limit in how often it calls pull, decompressing data 64K bytes at a time. The buffers are saved in the output list, and remain reachable until OOM is hit. This is fixed in versions 4.1.125.Final of netty-codec and 4.2.5.Final of netty-codec-compression.
|
| 1.1.20 | CVSS v3: 5.9 | spring-webmvc-6.2.9.jar | DATAGO-109375 | JAR |
Spring Framework MVC applications can be vulnerable to a “Path Traversal Vulnerability” when deployed on a non-compliant Servlet container.
|
| 1.1.20 | CVSS v3: 7.5 | tomcat-embed-core-10.1.43.jar | DATAGO-109131 | JAR |
Improper Resource Shutdown or Release vulnerability in Apache Tomcat made Tomcat vulnerable to the made you reset attack.
|
| 1.1.20 | CVSS v3: 5.9 | spring-beans-6.2.9.jar | DATAGO-109374 | JAR |
Spring Framework MVC applications can be vulnerable to a “Path Traversal Vulnerability” when deployed on a non-compliant Servlet container.
|
| 1.1.16 | CVSS v3: 5.3 | commons-lang3-3.17.0.jar | DATAGO-106220 | JAR |
Uncontrolled Recursion vulnerability in Apache Commons Lang.
|
| 1.1.13 | CVSS v3: 6.5 | spring-web-6.2.7.jar | DATAGO-104295 | JAR |
In Spring Framework, versions 6.0.x as of 6.0.5, versions 6.1.x and 6.2.x, an application is vulnerable to a reflected file download (RFD) attack when it sets a “Content-Disposition” header with a non-ASCII charset, where the filename attribute is derived from user-supplied input.
|
| 1.1.13 | CVSS v3: 6.5 | tomcat-embed-core-10.1.41.jar | DATAGO-104376 | JAR |
Allocation of Resources Without Limits or Throttling vulnerability in Apache Tomcat.
|
| 1.1.9 | CVSS v3: 3.1 | spring-context-6.2.6.jar | DATAGO-102515 | JAR |
CVE-2024-38820 ensured Locale-independent, lowercase conversion for both the configured disallowedFields patterns and for request parameter names. However, there are still cases where it is possible to bypass the disallowedFields checks.
|
| 1.1.9 | CVSS v3: 9.1 | spring-security-core-6.4.5.jar | DATAGO-102683 | JAR |
Spring Security Aspects may not correctly locate method security annotations on private methods. This can cause an authorization bypass.
|
| 1.1.6 | CVSS v3: 7.5 (HIGH) | DATAGO-100430 | Image |
In SQLite 3.44.0 through 3.49.0 before 3.49.1, the concat_ws() SQL function can cause memory to be written beyond the end of a malloc-allocated buffer. If the separator argument is attacker-controlled and has a large string (e.g., 2MB or more), an integer overflow occurs in calculating the size of the result buffer, and thus malloc may not allocate enough memory.
|
|
| 1.1.6 | CVSS v3: 7.5 | httpclient5-5.4.2.jar | DATAGO-99888 | JAR |
A bug in PSL validation logic in Apache HttpClient 5.4.x disables domain checks, affecting cookie management and host name verification. Discovered by the Apache HttpClient team. Fixed in the 5.4.3 release
|
| 1.1.3 | CVSS v3: 5.3 | spring-security-core-6.4.3.jar | DATAGO-97533 | JAR |
Spring Security 6.4.0 through 6.4.3 may not correctly locate method security annotations on parameterized types or methods. This may cause an authorization bypass. Your application may be affected by this if the following are true:
|
| 1.1.3 | CVSS v3: 7.4 | spring-security-crypto-6.4.3.jar | DATAGO-97534 | JAR |
BCryptPasswordEncoder.matches(CharSequence,String) will incorrectly return true for passwords larger than 72 characters as long as the first 72 characters are the same.
|
| 1.1.3 | CVSS v3: 0 (MEDIUM) | DATAGO-96844 | Image |
Bypass/Injection vulnerability in Apache Camel-Bean component under particular conditions. This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from 3.10.0 through <= 3.22.3. Users are recommended to upgrade to version 4.10.2 for 4.10.x LTS, 4.8.5 for 4.8.x LTS and 3.22.4 for 3.x releases. This vulnerability is only present in the following situation. The user is using one of the following HTTP Servers via one the of the following Camel components * camel-servlet * camel-jetty * camel-undertow * camel-platform-http * camel-netty-http and in the route, the exchange will be routed to a camel-bean producer. So ONLY camel-bean component is affected. In particular:u00a0 * The bean invocation (is only affected if you use any of the aboveu00a0together with camel-bean component). * The bean that can be called, hasu00a0more than 1 method implemented. In these conditions an attacker could be able to forge a Camel header name and make the bean component invoking other methods in the same bean. The vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with "Camel", "camel", or "org.apache.camel.".u00a0 Mitigation:u00a0You can easily work around this in your Camel applications by removing theu00a0headers in your Camel routes. There are many ways of doing this, alsou00a0globally or per route.
|
|
| 1.1.3 | CVSS v3: 6.5 | camel-support-4.9.0.jar | DATAGO-96844 | JAR |
Bypass/Injection vulnerability in Apache Camel.
|
| 1.1.3 | CVSS v3: 7.5 (HIGH) | DATAGO-96240 | Image |
Netty, an asynchronous, event-driven network application framework, has a vulnerability starting in version 4.1.91.Final and prior to version 4.1.118.Final. When a special crafted packet is received via SslHandler it doesn\'t correctly handle validation of such a packet in all cases which can lead to a native crash. Version 4.1.118.Final contains a patch. As workaround its possible to either disable the usage of the native SSLEngine or change the code manually.
|
|
| 1.1.0 | CVSS v3: 7.5 | netty-handler-4.1.117.Final.jar | DATAGO-94911 | JAR |
Netty, an asynchronous, event-driven network application framework, has a vulnerability starting in version 4.1.91.Final and prior to version 4.1.118.Final. When a special crafted packet is received via SslHandler it doesn't correctly handle validation of such a packet in all cases which can lead to a native crash. Version 4.1.118.Final contains a patch. As workaround its possible to either disable the usage of the native SSLEngine or change the code manually.
|
| 1.1.0 | CVSS v3: 7.5 | json-smart-2.5.1.jar | DATAGO-94030 | JAR |
A security issue was found in Netplex Json-smart 2.5.0 through 2.5.1. When loading a specially crafted JSON input, containing a large number of ’{’, a stack exhaustion can be trigger, which could allow an attacker to cause a Denial of Service (DoS). This issue exists because of an incomplete fix for CVE-2023-1370.
|
| 1.1.0 | CVSS v3: 5.5 | netty-common-4.1.117.Final.jar | DATAGO-94912 | JAR |
Netty, an asynchronous, event-driven network application framework, has a vulnerability in versions up to and including 4.1.118.Final. An unsafe reading of environment file could potentially cause a denial of service in Netty. When loaded on an Windows application, Netty attempts to load a file that does not exist. If an attacker creates such a large file, the Netty application crash. A similar issue was previously reported as CVE-2024-47535. This issue was fixed, but the fix was incomplete in that null-bytes were not counted against the input limit. Commit d1fbda62d3a47835d3fb35db8bd42ecc205a5386 contains an updated fix.
|
| 1.0.0 | CVSS v3: 5.5 | tomcat-embed-core-10.1.24.jar | DATAGO-79942 | JAR |
Improper Handling of Exceptional Conditions, Uncontrolled Resource Consumption vulnerability in Apache Tomcat. When processing an HTTP/2 stream, Tomcat did not handle some cases of excessive HTTP headers correctly. This led to a miscounting of active HTTP/2 streams which in turn led to the use of an incorrect infinite timeout which allowed connections to remain open which should have been closed.
|
| 1.0.0 | CVSS v3: 7.5 (HIGH) | DATAGO-79942 | Image |
Improper Handling of Exceptional Conditions, Uncontrolled Resource Consumption vulnerability in Apache Tomcat. When processing an HTTP/2 stream, Tomcat did not handle some cases of excessive HTTP headers correctly. This led to a miscounting of active HTTP/2 streams which in turn led to the use of an incorrect infinite timeout which allowed connections to remain open which should have been closed. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M20, from 10.1.0-M1 through 10.1.24, from 9.0.0-M1 through 9.0.89. Users are recommended to upgrade to version 11.0.0-M21, 10.1.25 or 9.0.90, which fixes the issue.
|
|
| 1.0.0 | CVSS v3: 7.5 (HIGH) | DATAGO-85256 | Image |
### Summary When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash. Reporter: Alexis Challande, Trail of Bits Ecosystem Security Team
|
|
| 1.0.0 | CVSS v3: 7.5 (HIGH) | DATAGO-73977 | JAR |
libexpat through 2.5.0 allows a denial of service (resource consumption) because many full reparsings are required in the case of a large token for which multiple buffer fills are needed.
|
|
| 1.0.0 | CVSS v3: 6.5 | spring-web-6.1.11.jar | DATAGO-82871 | JAR |
Spring Framework is vulnerable DoS via conditional HTTP request. Applications that parse ETags from "If-Match" or "If-None-Match" request headers are vulnerable to Denial of Service attack. All versions before 5.3.38, 6.0.23 and 6.1.12 are affected.
|
| 1.0.0 | CVSS v3: 4.4 | logback-core-1.5.12.jar | DATAGO-91429 | JAR |
ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core
|
| 1.0.0 | CVSS v3: 4.7 (MEDIUM) | DATAGO-67960 | Image |
jackson-databind through 2.15.2 allows attackers to cause a denial of service or other unspecified impact via a crafted object that uses cyclic dependencies. NOTE: the vendor\'s perspective is that this is not a valid vulnerability report, because the steps of constructing a cyclic data structure and trying to serialize it cannot be achieved by an external attacker.
|
|
| 1.0.0 | CVSS v3: 5.5 (MEDIUM) | DATAGO-74149 | JAR |
An issue was discovered in the FIPS Java API of Bouncy Castle BC-FJA before 1.0.2.4. Changes to the JVM garbage collector in Java 13 and later trigger an issue in the BC-FJA FIPS modules where it is possible for temporary keys used by the module to be zeroed out while still in use by the module, resulting in errors or potential information loss. NOTE: FIPS compliant users are unaffected because the FIPS certification is only for Java 7, 8, and 11.
|
|
| 1.0.0 | CVSS v3: 4.8 | spring-security-core-6.3.4.jar | DATAGO-89424 | JAR |
The usage of String.toLowerCase() and String.toUpperCase() has some Locale dependent exceptions that could potentially result in authorization rules not working properly.
|
| 1.0.0 | CVSS v3: 5.9 | bcprov-jdk18on-1.77.jar | DATAGO-75573 | JAR |
BouncyCastle before version 1.78 is vulnerable to timing side-channel attacks against RSA decryption (both PKCS#1v1.5 and OAEP).
|
| 1.0.0 | CVSS v3: 5.5 | netty-common-4.1.114.Final.jar | DATAGO-89346 | JAR |
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. An unsafe reading of environment file could potentially cause a denial of service in Netty. When loaded on an Windows application, Netty attempts to load a file that does not exist. If an attacker creates such a large file, the Netty application crashes. This vulnerability is fixed in 4.1.115.
|
| 1.0.0 | CVSS v3: 6.6 | logback-classic-1.5.12.jar | DATAGO-91430 | JAR |
ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core
|
| 1.0.0 | CVSS v3: 8.1 | spring-web-6.1.5.jar | DATAGO-75012 | JAR |
Applications that use UriComponentsBuilder to parse an externally provided URL (e.g. through a query parameter) AND perform validation checks on the host of the parsed URL may be vulnerable to a open redirect attack or to a SSRF attack if the URL is used after passing validation checks. This is the same as CVE-2024-22259 and CVE-2024-22243, but with different input.
|
| 1.0.0 | CVSS v3: 6.5 | spring-security-config-6.3.1.jar | DATAGO-83112 | JAR |
Missing Authorization When Using @AuthorizeReturnObject in Spring Security 6.3.0 and 6.3.1 allows attacker to render security annotations inaffective.
|
| 1.0.0 | CVSS v3: 9.8 | tomcat-embed-core-10.1.33.jar | DATAGO-91084 | JAR |
Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability during JSP compilation in Apache Tomcat permits an RCE on case insensitive file systems when the default servlet is enabled for write (non-default configuration).
|
| 1.0.0 | CVSS v3: 5.5 (MEDIUM) | DATAGO-78433 | JAR |
A use-after-free vulnerability was discovered in xasprintf function in xfuncs_printf.c:344 in BusyBox v.1.36.1.
|
|
| 1.0.0 | CVSS v3: 7.5 | spring-webmvc-6.1.12.jar | DATAGO-84986 | JAR |
Applications serving static resources through the functional web frameworks WebMvc.fn or WebFlux.fn are vulnerable to path traversal attacks. An attacker can craft malicious HTTP requests and obtain any file on the file system that is also accessible to the process in which the Spring application is running.
|
| 1.0.0 | CVSS v3: 7.5 | spring-webmvc-6.1.13.jar | DATAGO-87570 | JAR |
Applications serving static resources through the functional web frameworks WebMvc.fn or WebFlux.fn are vulnerable to path traversal attacks. An attacker can craft malicious HTTP requests and obtain any file on the file system that is also accessible to the process in which the Spring application is running.
|
For more details, refer to the Release Notes page for the individual
Solace Messaging APIs.