Waydeshi

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** MCPHub versions prior to 1.0.29 **Description** The PUT '/api/system-config' endpoint (handler `updateSystemConfig`) lacks an authorization check. While the endpoint is protected by authentication middleware and a rate limiter, it fails to verify if the user has administrative privileges by not inspecting the `req.user.isAdmin` variable. **Recommendations** Update to version 1.0.29.

**Name of the Vulnerable Software and Affected Versions** MCPHub versions prior to 1.0.32 **Description** The built-in prompt and resource controllers lack role checking. The endpoints 'POST /api/prompts*' and 'PUT /api/prompts*', as well as 'POST /api/resources*' and 'PUT /api/resources*', are accessible to authenticated users without administrative privileges because the handlers do not verify the `req.user` variable. Since the DAO singletons are prioritized over connected MCP servers in the `handleGetPromptRequest()` and `handleReadResourceRequest()` functions, a non-admin user can create, overwrite, or shadow global prompt templates and resources. This leads to an unauthorized integrity violation and can result in stored prompt injection into the LLM sessions of other users. **Recommendations** Update to version 1.0.32.

**Name of the Vulnerable Software and Affected Versions** qs versions 2.2.5 through 6.15.3 **Description** The `qs.stringify` function can throw a `TypeError` when serializing an object that contains a `constructor` property with a truthy, non-callable `isBuffer` member. This occurs because the `utils.isBuffer()` function performs duck-typing by invoking `obj.constructor.isBuffer(obj)` without first verifying that `isBuffer` is actually a function. An attacker can trigger this by providing specially crafted input via `qs.parse` (using `plainObjects: true` or `allowPrototypes: true`) or through `JSON.parse`. In environments like Express 4 or body-parser with `extended: true`, such input can be passed directly through `req.query` or `req.body`. This can lead to a denial of service where the affected request returns a 500 error, or in cases where the call occurs outside an error boundary (such as in an `async` handler), it may cause the entire process to exit. **Recommendations** Update qs to version 6.16.0 or later.