Overview 213 matches · 56 protected · 5 exploited · 2 CISA KEV · 8 public PoC · 8 EPSS ≥ 0.5
Protected by Waratek
56
26.3%
Rule in development
0
0.0%
Mitigation candidate
1
0.5%
No exploit published
156
73.2%
blocked by ARMR today
56
26.3%
partly blocked
0
0.0%
not blocked
157
73.7%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
5
2.3%
Working exploit published
0
0.0%
Proof of concept only
43
20.2%
Forecast only
1
0.5%
No public exploit
164
77.0%
split by
peak 31 / quarter
Q1 218
Protected by Waratek3
No exploit published5
Critical1
High2
Medium5
blocked by ARMR today3
not blocked5
Forecast only1
No public exploit7
Q2 214
Protected by Waratek3
No exploit published1
High1
Medium3
blocked by ARMR today3
not blocked1
No public exploit4
Q3 216
Protected by Waratek2
No exploit published4
High3
Medium3
blocked by ARMR today2
not blocked4
Exploited1
No public exploit5
Q4 2116
Protected by Waratek11
No exploit published5
Critical1
High3
Medium10
Low2
blocked by ARMR today11
not blocked5
Exploited3
Proof of concept only1
No public exploit12
Q1 2226
Protected by Waratek9
No exploit published17
Critical2
High3
Medium20
Low1
blocked by ARMR today9
not blocked17
Proof of concept only1
No public exploit25
Q2 229
Protected by Waratek5
No exploit published4
Critical1
High2
Medium5
Low1
blocked by ARMR today5
not blocked4
Proof of concept only3
No public exploit6
Q3 2210
Protected by Waratek4
No exploit published6
Critical1
High3
Medium5
Low1
blocked by ARMR today4
not blocked6
Proof of concept only1
No public exploit9
Q4 229
Protected by Waratek3
No exploit published6
High1
Medium6
Low2
blocked by ARMR today3
not blocked6
Proof of concept only2
No public exploit7
Q1 233
Protected by Waratek1
No exploit published2
High1
Medium2
blocked by ARMR today1
not blocked2
No public exploit3
Q2 2315
Protected by Waratek7
No exploit published8
High3
Medium9
Low3
blocked by ARMR today7
not blocked8
Proof of concept only1
No public exploit14
Q3 239
Protected by Waratek1
No exploit published8
High2
Medium4
Low3
blocked by ARMR today1
not blocked8
No public exploit9
Q4 2311
Mitigation candidate1
No exploit published10
High2
Medium9
not blocked11
Exploited1
Proof of concept only8
No public exploit2
Q1 241
No exploit published1
Medium1
not blocked1
Proof of concept only1
Q2 241
No exploit published1
Critical1
not blocked1
No public exploit1
Q3 242
No exploit published2
Critical1
High1
not blocked2
No public exploit2
Q4 242
No exploit published2
High1
Medium1
not blocked2
No public exploit2
Q1 251
No exploit published1
Medium1
not blocked1
No public exploit1
Q2 251
No exploit published1
High1
not blocked1
No public exploit1
Q3 255
Protected by Waratek1
No exploit published4
High1
Medium3
Low1
blocked by ARMR today1
not blocked4
Proof of concept only1
No public exploit4
Q4 256
Protected by Waratek2
No exploit published4
Critical2
High1
Medium3
blocked by ARMR today2
not blocked4
Proof of concept only2
No public exploit4
Q1 266
No exploit published6
High3
Medium3
not blocked6
Proof of concept only1
No public exploit5
Q2 2631
No exploit published31
Critical3
High17
Medium10
Low1
not blocked31
Proof of concept only10
No public exploit21
Q3 2624
Protected by Waratek4
No exploit published20
High15
Medium9
blocked by ARMR today4
not blocked20
Proof of concept only7
No public exploit17
Q4 267
No exploit published7
High5
Medium2
not blocked7
Proof of concept only4
No public exploit3
Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-3637 | High | 2021-07-09 | No exploit published | No public exploit | A flaw was found in keycloak-model-infinispan in keycloak versions before 14.0.0 where authenticationSessions map in RootAuthenticationSessionEntity grows boundlessly which could lead to a DoS attack. |
| CVE-2021-3522 | Medium | 2021-06-02 | No exploit published | No public exploit | GStreamer before 1.18.4 may perform an out-of-bounds read when handling certain ID3v2 tags. |
| CVE-2021-21656 | High | 2021-05-11 | Protected by Waratek | No public exploit | Jenkins Xcode integration Plugin 2.0.14 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. |
| CVE-2021-2161 | Medium | 2021-04-22 | Protected by Waratek | No public exploit | Vulnerability in the Java SE, Java SE Embedded, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Libraries). Supported versions that are affected are Java SE: 7u291, 8u281, 11.0.10, 16; Java SE Embedded: 8u281; Oracle GraalVM Enterprise Edition: 19.3.5, 20.3.1.2 and 21.0.0.2. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java SE, Java SE Embedded, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. It can also be exploited by supplying untrusted data to APIs in the specified Component. CVSS 3.1 Base Score 5.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N). |
| CVE-2021-29425 | Medium | 2021-04-13 | Protected by Waratek | No public exploit | In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value. |
| CVE-2021-21409 | Medium | 2021-03-30 | No exploit published | No public exploit | Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In Netty (io.netty:netty-codec-http2) before version 4.1.61.Final there is a vulnerability that enables request smuggling. The content-length header is not correctly validated if the request only uses a single Http2HeaderFrame with the endStream set to to true. This could lead to request smuggling if the request is proxied to a remote peer and translated to HTTP/1.1. This is a followup of GHSA-wm47-8v5p-wjpj/CVE-2021-21295 which did miss to fix this one case. This was fixed as part of 4.1.61.Final. |
| CVE-2021-20218 | High | 2021-03-16 | Protected by Waratek | No public exploit | A flaw was found in the fabric8 kubernetes-client in version 4.2.0 and after. This flaw allows a malicious pod/container to cause applications using the fabric8 kubernetes-client `copy` command to extract files outside the working path. The highest threat from this vulnerability is to integrity and system availability. This has been fixed in kubernetes-client-4.13.2 kubernetes-client-5.0.2 kubernetes-client-4.11.2 kubernetes-client-4.7.2 |
| CVE-2021-26987 | Critical | 2021-03-15 | Protected by Waratek | No public exploit | Element Plug-in for vCenter Server incorporates SpringBoot Framework. SpringBoot Framework versions prior to 1.3.2 are susceptible to a vulnerability which when successfully exploited could lead to Remote Code Execution. All versions of Element Plug-in for vCenter Server, Management Services versions prior to 2.17.56 and Management Node versions through 12.2 contain vulnerable versions of SpringBoot Framework. |
| CVE-2021-21364 | Medium | 2021-03-11 | No exploit published | No public exploit | swagger-codegen is an open-source project which contains a template-driven engine to generate documentation, API clients and server stubs in different languages by parsing your OpenAPI / Swagger definition. In swagger-codegen before version 2.4.19, on Unix-Like systems, the system temporary directory is shared between all local users. When files/directories are created, the default `umask` settings for the process are respected. As a result, by default, most processes/apis will create files/directories with the permissions `-rw-r--r--` and `drwxr-xr-x` respectively, unless an API that explicitly sets safe file permissions is used. Because this vulnerability impacts generated code, the generated code will remain vulnerable until fixed manually! This vulnerability is fixed in version 2.4.19. Note this is a distinct vulnerability from CVE-2021-21363. |
| CVE-2021-21363 | High | 2021-03-11 | No exploit published | No public exploit | swagger-codegen is an open-source project which contains a template-driven engine to generate documentation, API clients and server stubs in different languages by parsing your OpenAPI / Swagger definition. In swagger-codegen before version 2.4.19, on Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory. This vulnerability is local privilege escalation because the contents of the `outputFolder` can be appended to by an attacker. As such, code written to this directory, when executed can be attacker controlled. For more details refer to the referenced GitHub Security Advisory. This vulnerability is fixed in version 2.4.19. Note this is a distinct vulnerability from CVE-2021-21364. |
| CVE-2021-21295 | Medium | 2021-03-09 | No exploit published | No public exploit | Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In Netty (io.netty:netty-codec-http2) before version 4.1.60.Final there is a vulnerability that enables request smuggling. If a Content-Length header is present in the original HTTP/2 request, the field is not validated by `Http2MultiplexHandler` as it is propagated up. This is fine as long as the request is not proxied through as HTTP/1.1. If the request comes in as an HTTP/2 stream, gets converted into the HTTP/1.1 domain objects (`HttpRequest`, `HttpContent`, etc.) via `Http2StreamFrameToHttpObjectCodec `and then sent up to the child channel's pipeline and proxied through a remote peer as HTTP/1.1 this may result in request smuggling. In a proxy case, users may assume the content-length is validated somehow, which is not the case. If the request is forwarded to a backend channel that is a HTTP/1.1 connection, the Content-Length now has meaning and needs to be checked. An attacker can smuggle requests inside the body as it gets downgraded from HTTP/2 to HTTP/1.1. For an example attack refer to the linked GitHub Advisory. Users are only affected if all of this is true: `HTTP2MultiplexCodec` or `Http2FrameCodec` is used, `Http2StreamFrameToHttpObjectCodec` is used to convert to HTTP/1.1 objects, and these HTTP/1.1 objects are forwarded to another remote peer. This has been patched in 4.1.60.Final As a workaround, the user can do the validation by themselves by implementing a custom `ChannelInboundHandler` that is put in the `ChannelPipeline` behind `Http2StreamFrameToHttpObjectCodec`. |
| CVE-2020-27223 | Medium | 2021-02-26 | No exploit published | Forecast only | In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality” (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values. |
| CVE-2021-21290 | Medium | 2021-02-08 | Protected by Waratek | No public exploit | Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In Netty before version 4.1.59.Final there is a vulnerability on Unix-like systems involving an insecure temp file. When netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. On unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems. The method "File.createTempFile" on unix-like systems creates a random file, but, by default will create this file with the permissions "-rw-r--r--". Thus, if sensitive information is written to this file, other local users can read this information. This is the case in netty's "AbstractDiskHttpData" is vulnerable. This has been fixed in version 4.1.59.Final. As a workaround, one may specify your own "java.io.tmpdir" when you start the JVM or use "DefaultHttpDataFactory.setBaseDir(...)" to set the directory to something that is only readable by the current user. |