Find, fix and prevent vulnerabilities in your code.
critical severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.30.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to HTTP Request Smuggling due to the interaction of quotation marks and delimiters in the parseCookie() function. An attacker can exfiltrate HttpOnly cookie values or smuggle extra cookie values.
Remediation
Upgrade io.undertow:undertow-core to version 2.2.30.Final, 2.3.11.Final or higher.
References
high severity
- Vulnerable module: org.apache.commons:commons-lang3
- Introduced through: org.apache.commons:commons-text@1.10.0
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › org.apache.commons:commons-text@1.10.0 › org.apache.commons:commons-lang3@3.12.0Remediation: Upgrade to org.apache.commons:commons-text@1.14.0.
Overview
Affected versions of this package are vulnerable to Uncontrolled Recursion via the ClassUtils.getClass function. An attacker can cause the application to terminate unexpectedly by providing excessively long input values.
Remediation
Upgrade org.apache.commons:commons-lang3 to version 3.18.0 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-core
- Introduced through: com.fasterxml.jackson.core:jackson-core@2.14.1
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › com.fasterxml.jackson.core:jackson-core@2.14.1Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.15.0.
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 Denial of Service (DoS) due to missing input size validation when performing numeric type conversions. A remote attacker can exploit this vulnerability by causing the application to deserialize data containing certain numeric types with large values, causing the application to exhaust all available resources.
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.15.0-rc1 or higher.
References
high severity
- Vulnerable module: com.fasterxml.jackson.core:jackson-core
- Introduced through: com.fasterxml.jackson.core:jackson-core@2.14.1
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › com.fasterxml.jackson.core:jackson-core@2.14.1Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.15.0.
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 Stack-based Buffer Overflow due to the parse process, which accepts an unlimited input file with deeply nested data. An attacker can cause a stack overflow and crash the application by providing input files with excessively deep nesting.
Remediation
Upgrade com.fasterxml.jackson.core:jackson-core to version 2.15.0-rc1 or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.3.20.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling (MadeYouReset) through malformed client requests that trigger repeated server-side stream resets without incrementing abuse counters. An attacker can exhaust server resources by sending specially crafted HTTP/2 requests that cause excessive workload through repeated stream aborts.
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 io.undertow:undertow-core to version 2.3.20.Final or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.31.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Denial of Service (DoS) through the wildfly-http-client protocol, due to the WriteTimeoutStreamSinkConduit process. This vulnerability can be exploited by repeatedly opening and closing connections immediately, which triggers memory and file descriptor leaks.
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 io.undertow:undertow-core to version 2.2.31.Final, 2.3.12.Final or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.34.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Uncontrolled Recursion in chunked response handling. An attacker can cause a client to wait indefinitely by sending excessive data without a 0\r\n termination sequence in chunked responses, thereby disrupting service to the server.
Note: This is only exploitable when using NewSessionTicket functionality in TLS 1.3 on Java 17.
Remediation
Upgrade io.undertow:undertow-core to version 2.2.34.Final, 2.3.8.Final or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.33.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') through the handling of URL-encoded request path information on ajp-listener. An attacker can cause the server to process incorrect paths, leading to a disruption of service by sending specially crafted concurrent requests.
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 io.undertow:undertow-core to version 2.2.33.Final, 2.3.14.Final or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.33.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') due to insufficient limitations on the amount of CONTINUATION frames that can be sent within a single stream. An attacker can use up compute or memory resources to cause a disruption in service by sending packets to vulnerable servers.
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 io.undertow:undertow-core to version 2.2.33.Final, 2.3.14.Final or higher.
References
high severity
- Vulnerable module: net.minidev:json-smart
- Introduced through: com.nimbusds:oauth2-oidc-sdk@11.12
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › com.nimbusds:oauth2-oidc-sdk@11.12 › net.minidev:json-smart@2.5.1Remediation: Upgrade to com.nimbusds:oauth2-oidc-sdk@11.22.2.
Overview
net.minidev:json-smart is a Java JSON parser.
Affected versions of this package are vulnerable to Denial of Service (DoS). An attacker can cause a stack exhaustion and subsequent service disruption by providing JSON input with an excessive number of nested {.
Note:
This issue exists because of an incomplete fix for CVE-2023-1370.
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 net.minidev:json-smart to version 2.5.2 or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.31.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling. An attacker can disrupt service availability by repeatedly sending AJP requests that exceed the configured max-header-size attribute in ajp-listener, leading to the server closing the TCP connection without returning an AJP response.
Note:
This is only exploitable if the max-header-size is set to 64 KB or less.
Remediation
Upgrade io.undertow:undertow-core to version 2.2.31.Final, 2.3.12.Final or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.15.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Denial of Service (DoS) which would cause client side invocation timeout with certain calls made over HTTP2.
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 io.undertow:undertow-core to version 2.2.15.Final or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.18.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Denial of Service (DoS) via an AJP 400 response, when EAP 7 is improperly sending two response packets, those packets have the reuse flag set even though JBoss EAP closes the connection. A failure occurs when the connection is reused after a 400 by CPING since it reads in the second SEND_HEADERS response packet instead of a CPONG.
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 io.undertow:undertow-core to version 2.2.18, 2.3.0.Alpha2 or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.24.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Improper Certificate Validation via the undertow client which does not check the server identity presented by the server certificate in https connections.
Remediation
Upgrade io.undertow:undertow-core to version 2.2.24.Final, 2.3.5.Final or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.32.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Improper Input Validation via the FormAuthenticationMechanism. An attacker can exhaust the server's memory, leading to a Denial of Service by sending crafted requests that cause an OutofMemory error.
Remediation
Upgrade io.undertow:undertow-core to version 2.2.32.Final, 2.3.13.Final or higher.
References
high severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.27.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Memory Allocation with Excessive Size Value due to improper @MultipartConfig annotation handling for very large multipart content.
Note:
If the server uses fileSizeThreshold to limit the file size, it's possible to bypass the limit by setting the file name in the request to null.
Remediation
Upgrade io.undertow:undertow-core to version 2.2.27.Final, 2.3.9.Final or higher.
References
high severity
- Vulnerable module: org.jboss.xnio:xnio-api
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.Final › org.jboss.xnio:xnio-api@3.8.0.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.33.Final.
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.Final › org.jboss.xnio:xnio-nio@3.8.0.Final › org.jboss.xnio:xnio-api@3.8.0.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.33.Final.
Overview
org.jboss.xnio:xnio-api is a simplified low-level I/O layer which can be used anywhere you are using NIO.
Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') due to the NotifierState function that can cause a Stack Overflow Exception when the chain of notifier states becomes problematically large, leading to a possible denial of service.
Remediation
Upgrade org.jboss.xnio:xnio-api to version 3.5.10, 3.7.13, 3.8.14 or higher.
References
medium severity
- Vulnerable module: commons-io:commons-io
- Introduced through: commons-io:commons-io@2.11.0
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › commons-io:commons-io@2.11.0Remediation: Upgrade to commons-io:commons-io@2.14.0.
Overview
commons-io:commons-io is a The Apache Commons IO library contains utility classes, stream implementations, file filters, file comparators, endian transformation classes, and much more.
Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') through the XmlStreamReader class. An attacker can cause the application to consume excessive CPU resources by sending specially crafted XML content.
Remediation
Upgrade commons-io:commons-io to version 2.14.0 or higher.
References
medium severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.36.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Race Condition due to the reuse of the StringBuilder instance in the ProxyProtocolReadListener across multiple requests. An attacker can access data from previous requests or responses by exploiting the shared usage of the StringBuilder.
This vulnerability primarily results in errors and connection termination but creates a risk of data leakage in multi-request environments.
Remediation
Upgrade io.undertow:undertow-core to version 2.2.36.Final, 2.3.17.Final or higher.
References
medium severity
- Vulnerable module: org.jboss.xnio:xnio-api
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.Final › org.jboss.xnio:xnio-api@3.8.0.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.9.Final.
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.Final › org.jboss.xnio:xnio-nio@3.8.0.Final › org.jboss.xnio:xnio-api@3.8.0.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.9.Final.
Overview
org.jboss.xnio:xnio-api is a simplified low-level I/O layer which can be used anywhere you are using NIO.
Affected versions of this package are vulnerable to Denial of Service (DoS). A vulnerability was discovered in XNIO where file descriptor leak caused by growing amounts of NIO Selector file handles between garbage collection cycles. It may allow the attacker to cause a denial of service.
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 org.jboss.xnio:xnio-api to version 3.8.1.Final, 3.7.8.Final or higher.
References
medium severity
- Vulnerable module: com.beust:jcommander
- Introduced through: com.beust:jcommander@1.72
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › com.beust:jcommander@1.72Remediation: Upgrade to com.beust:jcommander@1.75.
Overview
com.beust:jcommander is a Command line parsing framework for Java.
Affected versions of this package are vulnerable to Unsafe Dependency Resolution due to resolving dependencies over an insecure channel (http).
If the build occurred over an insecure connection, a malicious user could have perform a Man-in-the-Middle attack during the build and alter the build artifacts that were produced. In the case that any of these artifacts were compromised, any developers using them could be vulnerable.
Note: In order to validate that this artifact was not compromised, the maintainer would need to confirm that all of the artifacts published to the registry were not altered. Until this happens, we can not guarantee that this artifact was not compromised even though the probability that this happened is low.
We have chosen to alert on this issue when maintainers either decided to issue CVEs themselves, or in cases when maintainers decided against performing audits on their build to verify they had not been compromised.
Remediation
Upgrade com.beust:jcommander to version 1.75 or higher.
References
medium severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.11.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to an issue in the flow control handling by the browser over http/2.
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 io.undertow:undertow-core to version 2.0.40.Final, 2.2.11.Final or higher.
References
medium severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.19.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Denial of Service (DoS) when a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize). The AjpServerRequestConduit implementation closes a connection without sending any response to the client/proxy which will result in a front-end proxy marking the backend worker as an error state and not forward requests to the worker for a while.
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 io.undertow:undertow-core to version 2.2.19.Final, 2.3.0.Alpha2 or higher.
References
medium severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.25.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Denial of Service (DoS) in flow control handling by the browser over HTTP/2. This may cause overhead or a denial of service in the server. This is due to an incomplete fix of CVE-2021-3629.
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 io.undertow:undertow-core to version 2.2.25.Final, 2.3.6.Final or higher.
References
medium severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.33.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Directory Traversal due to improper input validation of the HTTP request. An attacker can access privileged or restricted files and directories by appending a specially-crafted sequence to an HTTP request for an application deployed to JBoss EAP.
Details
A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.
Directory Traversal vulnerabilities can be generally divided into two types:
- Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.
st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.
If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.
curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa
Note %2e is the URL encoded version of . (dot).
- Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as
Zip-Slip.
One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.
The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:
2018-04-15 22:04:29 ..... 19 19 good.txt
2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys
Remediation
Upgrade io.undertow:undertow-core to version 2.2.33.Final, 2.3.12.Final or higher.
References
medium severity
- Vulnerable module: org.jboss.xnio:xnio-api
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.Final › org.jboss.xnio:xnio-api@3.8.0.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.33.Final.
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.Final › org.jboss.xnio:xnio-nio@3.8.0.Final › org.jboss.xnio:xnio-api@3.8.0.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.33.Final.
Overview
org.jboss.xnio:xnio-api is a simplified low-level I/O layer which can be used anywhere you are using NIO.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the notifyReadClosed method by allowing an attacker to send flawed requests to a server, possibly causing log contention-related performance concerns or an unwanted disk fill-up.
Remediation
Upgrade org.jboss.xnio:xnio-api to version 3.8.8 or higher.
References
low severity
- Vulnerable module: io.undertow:undertow-core
- Introduced through: io.undertow:undertow-core@2.2.8.Final
Detailed paths
-
Introduced through: carbynestack/cli@carbynestack/cli#f7c5f3972765c937df46950aa25e043b68761359 › io.undertow:undertow-core@2.2.8.FinalRemediation: Upgrade to io.undertow:undertow-core@2.2.37.Final.
Overview
io.undertow:undertow-core is a Java web server based on non-blocking IO.
Affected versions of this package are vulnerable to Memory Leak when the learning-push handler is configured with the default maxAge of -1. An attacker who can send normal HTTP requests may consume excessive memory.
Workaround
This vulnerability can be avoided by setting a value for maxAge that is not -1.
Remediation
Upgrade io.undertow:undertow-core to version 2.2.37.Final, 2.3.18.Final or higher.