Vmware Spring Framework 5.3.25

CPE Details

Vmware Spring Framework 5.3.25
5.3.25
2023-02-06
22h16 +00:00
2023-02-06
22h19 +00:00
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:vmware:spring_framework:5.3.25:*:*:*:*:*:*:*

Informations

Vendor

vmware

Product

spring_framework

Version

5.3.25

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2024-38820 2024-10-18 05h39 +00:00 The fix for CVE-2022-22968 made disallowedFields patterns in DataBinder case insensitive. However, String.toLowerCase() has some Locale dependent exceptions that could potentially result in fields not protected as expected.
5.3
Moyen
CVE-2023-44794 2023-10-24 22h00 +00:00 An issue in Dromara SaToken version 1.36.0 and before allows a remote attacker to escalate privileges via a crafted payload to the URL.
9.8
Critique
CVE-2023-20863 2023-04-13 00h00 +00:00 In spring framework versions prior to 5.2.24 release+ ,5.3.27+ and 6.0.8+ , it is possible for a user to provide a specially crafted SpEL expression that may cause a denial-of-service (DoS) condition.
6.5
Moyen
CVE-2023-20860 2023-03-27 00h00 +00:00 Spring Framework running version 6.0.0 - 6.0.6 or 5.3.0 - 5.3.25 using "**" as a pattern in Spring Security configuration with the mvcRequestMatcher creates a mismatch in pattern matching between Spring Security and Spring MVC, and the potential for a security bypass.
7.5
Haute
CVE-2023-20861 2023-03-23 00h00 +00:00 In Spring Framework versions 6.0.0 - 6.0.6, 5.3.0 - 5.3.25, 5.2.0.RELEASE - 5.2.22.RELEASE, and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial-of-service (DoS) condition.
6.5
Moyen
CVE-2016-1000027 2020-01-01 23h00 +00:00 Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required. NOTE: the vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data.
9.8
Critique