WaratekVRT Sign in
Reset
More filters (2)
Columns
Published from 2025-04-01✕Product: Spring✕
Overview 202 matches · 21 protected · 1 exploited · 0 CISA KEV · 4 public PoC · 0 EPSS ≥ 0.5
202matches 21protected10.4% 1exploited0.5% 0CISA KEV0.0% 4public PoC2.0% 0EPSS ≥ 0.50.0%
split by peak 76 / month
No exploit published: 178Mitigation candidate: 3Protected by Waratek: 21 Low: 15Medium: 86High: 81Critical: 20 not blocked: 181blocked by ARMR today: 21 No public exploit: 198Proof of concept only: 1Working exploit published: 2Exploited: 1
Apr 25Jun 25Aug 25Oct 25Dec 25Feb 26Apr 26Jun 26Aug 26
202 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 3 of 3 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2025-22233 Low 2025-05-16 No exploit published No public exploit CVE-2024-38820 ensured Locale-independent, lowercase conversion for both the configured disallowedFields patterns and for request parameter names. However, there are still cases where it is possible to bypass the disallowedFields checks. Affected Spring Products and Versions Spring Framework: * 6.2.0 - 6.2.6 * 6.1.0 - 6.1.19 * 6.0.0 - 6.0.27 * 5.3.0 - 5.3.42 * Older, unsupported versions are also affected Mitigation Users of affected versions should upgrade to the corresponding fixed version. Affected version(s)Fix Version Availability 6.2.x 6.2.7 OSS6.1.x 6.1.20 OSS6.0.x 6.0.28 Commercial https://enterprise.spring.io/ 5.3.x 5.3.43 Commercial https://enterprise.spring.io/ No further mitigation steps are necessary. Generally, we recommend using a dedicated model object with properties only for data binding, or using constructor binding since constructor arguments explicitly declare what to bind together with turning off setter binding through the declarativeBinding flag. See the Model Design section in the reference documentation. For setting binding, prefer the use of allowedFields (an explicit list) over disallowedFields. Credit This issue was responsibly reported by the TERASOLUNA Framework Development Team from NTT DATA Group Corporation.
CVE-2025-22235 High 2025-04-28 No exploit published No public exploit EndpointRequest.to() creates a matcher for null/** if the actuator endpoint, for which the EndpointRequest has been created, is disabled or not exposed. Your application may be affected by this if all the following conditions are met: * You use Spring Security * EndpointRequest.to() has been used in a Spring Security chain configuration * The endpoint which EndpointRequest references is disabled or not exposed via web * Your application handles requests to /null and this path needs protection You are not affected if any of the following is true: * You don't use Spring Security * You don't use EndpointRequest.to() * The endpoint which EndpointRequest.to() refers to is enabled and is exposed * Your application does not handle requests to /null or this path does not need protection
‹ prev page 3 of 3 next ›