Synopsys: Automated PR: Update org.springframework:spring-web:4.2.3.RELEASE to 4.2.5.RELEASE #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Automated PR Comment From BlackDuck❌ Found dependencies violating policy!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Vulnerabilities associated with org.springframework:spring-web:4.2.3.RELEASE
BDSA-2022-0858 (CRITICAL): Spring Framework is vulnerable to a flaw in the access restrictions to the security sensitive
ClassLoaderproperty. The restrictions can be bypassed through alternative paths available with Java9 and later. An attacker can leverage this vulnerability to cause remote code execution (RCE).Note this issue exists because the restrictions that were introduced to prevent exploitation of BDSA-2010-0001 (CVE-2010-1622) can be bypassed on platforms where Java9 and later are in use.
This vulnerability is listed as exploitable by the Cybersecurity & Infrastructure Security Agency in their Known Exploited Vulnerabilities Catalog.
BDSA-2016-0002 (HIGH): Spring Framework is vulnerable to path traversal. Paths provided to the
Resourceservletwere not properly sanitized and as a result exposed to directory traversal attacks.ResourceServletis now deprecated andResourceHttpRequestHandler(and related classes) have superseded it.BDSA-2016-1700 (HIGH): Pivotal's Spring Framework contains an unsafe Java deserialization vulnerability. If the Spring Framework library's
HttpInvokerServiceExporteris being used to deserialize client data, it may be possible for a remote attacker to perform remote code execution (RCE) on systems using Spring Framework.Note: All versions prior to 6.0.0-M1 (Which is a pre-release) contain the functionality that may lead to deserialization attacks depending on how the library is implemented in the product.
BDSA-2018-0994 (HIGH): Spring Framework is vulnerable to remote code execution (RCE) due to lack of proper validation of user-supplied input. Potential attackers can leverage this flaw to run arbitrary code on the target system by sending crafted messages.
BDSA-2022-0847 (HIGH): Software systems using Spring Framework may be vulnerable to unsafe deserialization if they employ unsafe use of certain provided deserialization functionality. A remote attacker could potentially execute arbitrary code on a vulnerable endpoint by passing a maliciously crafted serialized object to that endpoint.
Note: This issue only affects software that has been written to leverage specific deserialization functionality provided by the Spring Framework without sanitization.
BDSA-2018-1042 (HIGH): Spring Framework is vulnerable to remote code execution (RCE) due to lack of proper validation of user-supplied input. Potential attackers can leverage this flaw to run arbitrary code on the target system by sending crafted messages. Original remediation was not implemented correctly for the 4.3.x branch.
BDSA-2018-3577 (MEDIUM): An improper input validation vulnerability has been discovered in Spring Framework by Pivotal. A range header input is not being correctly restricted allowing a high value to be accepted by the application. An attacker could exploit this vulnerability to cause a denial-of-service (DoS) condition.
This vulnerability affects applications that depend on either
spring-webmvcorspring-webflux.BDSA-2018-1901 (MEDIUM): Spring Framework is vulnerable to information exposure due to improper configuration of JSON with Padding (JSONP). This could allow an attacker to obtain potentially sensitive information.
BDSA-2018-1960 (MEDIUM): A cross-site tracing (XST) vulnerability has been discovered in spring framework. The application allows obscure request methods, such as TRACE and TRACK. These HTTP methods can be used with an existing cross-site scripting (XSS) vulnerability to escalate to an XST vulnerability. An attacker could exploit this by utilizing an XSS vulnerability to bypass cookie protection and steal sensitive data.
BDSA-2018-1440 (MEDIUM): Spring Framework has a flaw in the manipulation of regular expressions within the spring-messaging module. An attacker can send a specially crafted message to the simple STOMP broker that will trigger a regular expression denial-of-service (ReDoS).
BDSA-2020-2431 (MEDIUM): It was discovered that Spring Framework was vulnerable to RFD protection bypass. In some instances, depending on the browser used, an attacker could bypass the RFD attack protections via the use of a
jsessionidpath parameter.BDSA-2021-3236 (MEDIUM): Spring Framework is vulnerable to log file injection due to the insufficient validation of user input in an undisclosed component. An attacker could leverage this issue in order to add arbitrary entries to a log file which could impact both the integrity issues and performance issues.
Note: a follow-up to this issue was disclosed as CVE-2021-22060 (BDSA-2021-3236), with further fixed releases that protect against additional types of input and in more places of the Spring Framework codebase.
BDSA-2022-0011 (MEDIUM): Spring Framework is vulnerable to log file injection due to the insufficient validation of user input in an undisclosed component. An attacker could leverage this issue in order to add arbitrary entries to a log file which could impact both the integrity issues and performance issues.
Note: the vendor states this issue exists as a follow up to CVE-2021-22096 (BDSA-2022-0011) that protects against additional types of input and in more places of the Spring Framework codebase.
BDSA-2022-0820 (MEDIUM): Spring-Framework's spring-expression is vulnerable to a denial-of-service (DoS) condition. This allows an attacker to use crafted input to cause the spring-expression process to crash due to an exception.
BDSA-2018-1013 (MEDIUM): Spring Framework is vulnerable to directory traversal due to the way static content can be loaded. Potential attackers could leverage this flaw to gain unauthorized access to sensitive files on Windows hosts.
BDSA-2016-1577 (MEDIUM): The Spring Framework contains a flaw when handling URL pattern mappings. The component fails to maintain the intended authorization for mapping requests to controllers. This could allow a remote attacker to bypass authentication and read protected files.
BDSA-2023-0638 (MEDIUM): Spring Framework is vulnerable to denial-of-service (DoS) via specially crafted SpEL expressions. An attacker could exploit this issue by passing a crafted SpEL expression to the application which may result in a crash.
BDSA-2023-0847 (MEDIUM): Spring Framework is vulnerable to denial-of-service (DoS) via specially crafted SpEL expressions.
Click Here To See More Details On Server