Pjfanning

jackson-databind binds a JSON string to a javax.xml.datatype.Duration or javax.xml.datatype.XMLGregorianCalendar field by passing the raw string verbatim to DatatypeFactory.newDuration(value) or newXMLGregorianCalendar(value) in CoreXMLDeserializers.Std. deserialize. These deserializers are registered by default with no opt-in, so a plain ObjectMapper or JsonMapper with no polymorphic typing and no special configuration reaches this path. The XML Schema lexical grammar permits numeric components of arbitrary length, which the JDK materializes through the native BigInteger(String) and BigDecimal(String) constructors, both quadratic in digit count. Because the digits sit inside a JSON string token rather than a JSON number token, jackson-core's StreamReadConstraints.maxNumberLength guard never applies; jackson's own NumberDeserializers call validateIntegerLength or validateFPLength before parsing a stringified number, but the XML datatype deserializer omits that pre-check. An unauthenticated attacker can therefore submit a single request of a few megabytes, such as a Duration value consisting of the letter P followed by several million digits and the letter Y, and force tens of seconds to several minutes of single-threaded CPU work; a handful of concurrent requests can saturate a server's worker threads. This affects com.fasterxml.jackson.core:jackson-databind from 2.0.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2.

**Name of the Vulnerable Software and Affected Versions** com.fasterxml.jackson.core:jackson-databind versions 2.8.0 through 2.18.9 com.fasterxml.jackson.core:jackson-databind versions 2.19.0 through 2.21.5 com.fasterxml.jackson.core:jackson-databind versions 2.22.0 through 2.22.1 tools.jackson.core:jackson-databind versions 3.0.0 through 3.1.5 tools.jackson.core:jackson-databind versions 3.2.0 through 3.2.1 **Description** The deserializer for java.nio.file.Path resolves an attacker-supplied URI without restricting the URI scheme. In the `JDKFromStringDeserializer.NioPathHelper.deserialize` function, a string from untrusted JSON is passed to `new URI(value)` and then to `Path.of(uri)`. If a `FileSystemNotFoundException` occurs, the code enumerates `ServiceLoader<FileSystemProvider>` and calls `provider.getPath(uri)` on the first provider matching the attacker-chosen scheme. This allows untrusted JSON to select and drive an arbitrary registered `FileSystemProvider` during `readValue` under a default `JsonMapper`, forcing provider class loading. While the resolved path is inert with only JDK built-in providers (file, jar/zipfs), further impact is possible if a side-effecting third-party `FileSystemProvider` is present on the classpath. **Recommendations** Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.18.10 Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.21.6 Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.22.2 Upgrade tools.jackson.core:jackson-databind to version 3.1.6 Upgrade tools.jackson.core:jackson-databind to version 3.2.2 Avoid binding java.nio.file.Path from untrusted JSON regardless of the version used.

**Name of the Vulnerable Software and Affected Versions** jackson-core versions 2.15.0 through 2.18.5 jackson-core versions 2.19.0 through 2.21.0 jackson-core versions 3.0.0 through 3.0.x **Description** The non-blocking (asynchronous) JSON parser in jackson-core fails to enforce the `maxNumberLength` constraint defined in `StreamReadConstraints`. This occurs because the async parsing path in `NonBlockingUtf8JsonParserBase` and related classes does not invoke number length validation methods. Specifically, methods like ` finishNumberIntegralPart()` accumulate digits into the `TextBuffer` without checks, and ` valueComplete()` fails to call `resetInt()` or `resetFloat()`, where `validateIntegerLength()` and `validateFPLength()` are executed. An attacker can submit a JSON document containing a number token of arbitrary length, leading to excessive memory allocation in the `TextBuffer` and potential `OutOfMemoryError`. Additionally, if the application calls `getBigIntegerValue()` or `getDecimalValue()`, the JVM may experience CPU exhaustion due to O(n^2) BigInteger parsing, resulting in a denial of service. **Recommendations** For jackson-core versions 2.15.0 through 2.18.5, update to a version where the `maxNumberLength` constraint is enforced in the async parser. For jackson-core versions 2.19.0 through 2.21.0, update to a version where the `maxNumberLength` constraint is enforced in the async parser. For jackson-core versions 3.0.0 through 3.0.x, update to a version where the `maxNumberLength` constraint is enforced in the async parser.

Name of the Vulnerable Software and Affected Versions: jackson-core versions prior to 2.15.0 Description: The issue arises when parsing input files with deeply nested data, potentially causing a StackoverflowError due to excessive depth. A configurable limit for traversal depth has been introduced, defaulting to 1000, to prevent this error. If the limit is reached, a StreamConstraintsException is thrown. Users should avoid parsing input files from untrusted sources as a workaround. Recommendations: For versions prior to 2.15.0, update to version 2.15.0 or later to include the configurable depth limit and prevent StackoverflowError. As a temporary workaround, consider avoiding the parsing of deeply nested input files from untrusted sources until the update is applied.

**Name of the Vulnerable Software and Affected Versions** H2 Database Engine versions prior to 2.2.220 **Description** The web-based admin console in H2 Database Engine can be started via the CLI with the argument `-webAdminPassword`, which allows the user to specify the password in cleartext for the web admin console. Consequently, a local user (or an attacker that has obtained local access through some means) would be able to discover the password by listing processes and their arguments. The issue was fixed in version 2.2.220. **Recommendations** For H2 Database Engine versions prior to 2.2.220, update to version 2.2.220 or later to resolve the issue. As a temporary workaround, consider avoiding the use of the `-webAdminPassword` argument when starting the web-based admin console via the CLI to minimize the risk of password exposure.

**Name of the Vulnerable Software and Affected Versions** xlsx-streamer versions prior to 2.1.0 **Description** The issue concerns the XML parser used in the Excel-Streaming-Reader, which did not apply all necessary settings to prevent XML Entity Expansion issues. This problem is resolved by upgrading to version 2.1.0. There is no known workaround for this issue. **Recommendations** Upgrade to version 2.1.0 to receive a patch. As there is no known workaround, upgrading to the specified version is the recommended course of action to mitigate the risk associated with this issue.