Overview 212 matches · 27 protected · 0 exploited · 0 CISA KEV · 7 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
27
12.7%
Rule in development
0
0.0%
Mitigation candidate
5
2.4%
No exploit published
180
84.9%
blocked by ARMR today
27
12.7%
partly blocked
0
0.0%
not blocked
185
87.3%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
0.5%
Proof of concept only
9
4.2%
Forecast only
0
0.0%
No public exploit
202
95.3%
split by
peak 82 / quarter
Q2 226
Protected by Waratek1
Mitigation candidate2
No exploit published3
Critical2
High1
Medium3
blocked by ARMR today1
not blocked5
Proof of concept only2
No public exploit4
Q3 221
No exploit published1
Low1
not blocked1
No public exploit1
Q4 225
Protected by Waratek2
Mitigation candidate1
No exploit published2
Critical4
High1
blocked by ARMR today2
not blocked3
Proof of concept only1
No public exploit4
Q1 234
No exploit published4
High2
Medium2
not blocked4
No public exploit4
Q2 235
No exploit published5
Critical1
High1
Medium3
not blocked5
No public exploit5
Q3 235
Protected by Waratek1
No exploit published4
Critical1
High2
Medium2
blocked by ARMR today1
not blocked4
Proof of concept only1
No public exploit4
Q4 234
Protected by Waratek1
No exploit published3
High2
Medium2
blocked by ARMR today1
not blocked3
Proof of concept only2
No public exploit2
Q1 245
Protected by Waratek2
No exploit published3
High3
Medium2
blocked by ARMR today2
not blocked3
No public exploit5
Q2 240
Q3 243
Protected by Waratek2
No exploit published1
Critical1
High1
Medium1
blocked by ARMR today2
not blocked1
No public exploit3
Q4 241
No exploit published1
Medium1
not blocked1
No public exploit1
Q1 250
Q2 250
Q3 250
Q4 250
Q1 2612
Protected by Waratek1
Mitigation candidate2
No exploit published9
Critical2
High8
Medium1
Low1
blocked by ARMR today1
not blocked11
Working exploit published1
Proof of concept only1
No public exploit10
Q2 2682
Protected by Waratek9
No exploit published73
Critical6
High38
Medium36
Low2
blocked by ARMR today9
not blocked73
No public exploit82
Q3 2676
Protected by Waratek8
No exploit published68
Critical10
High22
Medium34
Low10
blocked by ARMR today8
not blocked68
No public exploit76
Q4 263
No exploit published3
High1
Medium2
not blocked3
Proof of concept only2
No public exploit1
Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-38652 | Critical | 2022-11-12 | Protected by Waratek | No public exploit | A remote insecure deserialization vulnerability exixsts in VMWare Hyperic Agent 5.8.6. Exploitation of this vulnerability enables a malicious authenticated user to run arbitrary code or malware within a Hyperic Agent instance and its host operating system with the privileges of the Hyperic Agent process (often SYSTEM on Windows platforms). NOTE: prior exploitation of CVE-2022-38650 results in the disclosure of the authentication material required to exploit this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. |
| CVE-2022-38651 | Critical | 2022-11-12 | No exploit published | No public exploit | A security filter misconfiguration exists in VMware Hyperic Server 5.8.6. Exploitation of this vulnerability enables a malicious party to bypass some authentication requirements when issuing requests to Hyperic Server. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. |
| CVE-2022-38650 | Critical | 2022-11-12 | Protected by Waratek | No public exploit | A remote unauthenticated insecure deserialization vulnerability exists in VMware Hyperic Server 5.8.6. Exploitation of this vulnerability enables a malicious party to run arbitrary code or malware within Hyperic Server and the host operating system with the privileges of the Hyperic server process. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. |
| CVE-2022-31692 | Critical | 2022-10-31 | Mitigation candidate | Proof of concept only | Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or include dispatcher types. Specifically, an application is vulnerable when all of the following are true: The application expects that Spring Security applies security to forward and include dispatcher types. The application uses the AuthorizationFilter either manually or via the authorizeHttpRequests() method. The application configures the FilterChainProxy to apply to forward and/or include requests (e.g. spring.security.filter.dispatcher-types = request, error, async, forward, include). The application may forward or include the request to a higher privilege-secured endpoint.The application configures Spring Security to apply to every dispatcher type via authorizeHttpRequests().shouldFilterAllDispatcherTypes(true) |
| CVE-2022-31690 | High | 2022-10-31 | No exploit published | No public exploit | Spring Security, versions 5.7 prior to 5.7.5, and 5.6 prior to 5.6.9, and older unsupported versions could be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can modify a request initiated by the Client (via the browser) to the Authorization Server which can lead to a privilege escalation on the subsequent approval. This scenario can happen if the Authorization Server responds with an OAuth2 Access Token Response containing an empty scope list (per RFC 6749, Section 5.1) on the subsequent request to the token endpoint to obtain the access token. |
| CVE-2022-31679 | Low | 2022-09-21 | No exploit published | No public exploit | Applications that allow HTTP PATCH access to resources exposed by Spring Data REST in versions 3.6.0 - 3.5.5, 3.7.0 - 3.7.2, and older unsupported versions, if an attacker knows about the structure of the underlying domain model, they can craft HTTP requests that expose hidden entity attributes. |
| CVE-2022-22980 | Critical | 2022-06-23 | Mitigation candidate | Proof of concept only | A Spring Data MongoDB application is vulnerable to SpEL Injection when using @Query or @Aggregation-annotated query methods with SpEL expressions that contain query parameter placeholders for value binding if the input is not sanitized. |
| CVE-2022-22979 | High | 2022-06-21 | No exploit published | No public exploit | In Spring Cloud Function versions prior to 3.2.6, it is possible for a user who directly interacts with framework provided lookup functionality to cause a denial-of-service condition due to the caching issue in the Function Catalog component of the framework. |
| CVE-2022-22978 | Critical | 2022-05-19 | Mitigation candidate | Proof of concept only | In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be misconfigured to be bypassed on some servlet containers. Applications using RegexRequestMatcher with `.` in the regular expression are possibly vulnerable to an authorization bypass. |
| CVE-2022-22976 | Medium | 2022-05-19 | No exploit published | No public exploit | Spring Security versions 5.5.x prior to 5.5.7, 5.6.x prior to 5.6.4, and earlier unsupported versions contain an integer overflow vulnerability. When using the BCrypt class with the maximum work factor (31), the encoder does not perform any salt rounds, due to an integer overflow error. The default settings are not affected by this CVE. |
| CVE-2022-22971 | Medium | 2022-05-12 | Protected by Waratek | No public exploit | In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, application with a STOMP over WebSocket endpoint is vulnerable to a denial of service attack by an authenticated user. |
| CVE-2022-22970 | Medium | 2022-05-12 | No exploit published | No public exploit | In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object. |