Overview 21 matches · 5 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
21matches
5in Waratek scope23.8%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
5
23.8%
Outside Waratek scope
0
0.0%
Not applicable
16
76.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
21
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
21
100.0%
split by
peak 4 / quarter
Q3 191
Not applicable1
High1
not blocked1
No public exploit1
Q4 194
No exploit published1
Not applicable3
Critical1
Medium3
not blocked4
No public exploit4
Q1 201
No exploit published1
High1
not blocked1
No public exploit1
Q2 200
Q3 200
Q4 201
Not applicable1
Medium1
not blocked1
No public exploit1
Q1 213
Not applicable3
Medium3
not blocked3
No public exploit3
Q2 210
Q3 210
Q4 211
Not applicable1
High1
not blocked1
No public exploit1
Q1 220
Q2 222
Not applicable2
High1
Low1
not blocked2
No public exploit2
Q3 222
No exploit published2
Medium2
not blocked2
No public exploit2
Q4 220
Q1 230
Q2 232
Not applicable2
High1
Low1
not blocked2
No public exploit2
Q3 230
Q4 232
Not applicable2
Critical2
not blocked2
No public exploit2
Q1 240
Q2 240
Q3 240
Q4 241
No exploit published1
Medium1
not blocked1
No public exploit1
Q1 251
Not applicable1
Medium1
not blocked1
No public exploit1
Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24Q3 24Q1 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-29904 | Medium | 2025-03-12 | Not applicable | No public exploit | In JetBrains Ktor before 3.1.1 an HTTP Request Smuggling was possible |
| CVE-2024-49580 | Medium | 2024-10-17 | No exploit published | No public exploit | In JetBrains Ktor before 2.3.13 improper caching in HttpCache Plugin could lead to response information disclosure |
| CVE-2023-45613 | Critical | 2023-10-09 | Not applicable | No public exploit | In JetBrains Ktor before 2.3.5 server certificates were not verified |
| CVE-2023-45612 | Critical | 2023-10-09 | Not applicable | No public exploit | In JetBrains Ktor before 2.3.5 default configuration of ContentNegotiation with XML format was vulnerable to XXE |
| CVE-2023-34339 | Low | 2023-06-01 | Not applicable | No public exploit | In JetBrains Ktor before 2.3.1 headers containing authentication data could be added to the exception's message |
| CVE-2022-48476 | High | 2023-04-24 | Not applicable | No public exploit | In JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible |
| CVE-2022-38180 | Medium | 2022-08-12 | No exploit published | No public exploit | In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases |
| CVE-2022-38179 | Medium | 2022-08-12 | No exploit published | No public exploit | JetBrains Ktor before 2.1.0 was vulnerable to the Reflect File Download attack |
| CVE-2022-29930 | High | 2022-05-12 | Not applicable | No public exploit | SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. The issue was fixed in Ktor version 2.0.1. |
| CVE-2022-29035 | Low | 2022-04-11 | Not applicable | No public exploit | In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations |
| CVE-2021-43203 | High | 2021-11-09 | Not applicable | No public exploit | In JetBrains Ktor before 1.6.4, nonce verification during the OAuth2 authentication process is implemented improperly. |
| CVE-2021-25763 | Medium | 2021-02-03 | Not applicable | No public exploit | In JetBrains Ktor before 1.4.2, weak cipher suites were enabled by default. |
| CVE-2021-25762 | Medium | 2021-02-03 | Not applicable | No public exploit | In JetBrains Ktor before 1.4.3, HTTP Request Smuggling was possible. |
| CVE-2021-25761 | Medium | 2021-02-03 | Not applicable | No public exploit | In JetBrains Ktor before 1.5.0, a birthday attack on SessionStorage key was possible. |
| CVE-2020-26129 | Medium | 2020-11-16 | Not applicable | No public exploit | In JetBrains Ktor before 1.4.1, HTTP request smuggling was possible. |
| CVE-2020-5207 | High | 2020-01-27 | No exploit published | No public exploit | In Ktor before 1.3.0, request smuggling is possible when running behind a proxy that doesn't handle Content-Length and Transfer-Encoding properly or doesn't handle \n as a headers separator. |
| CVE-2019-19389 | Medium | 2019-12-26 | Not applicable | No public exploit | JetBrains Ktor framework before version 1.2.6 was vulnerable to HTTP Response Splitting. |
| CVE-2019-19703 | Medium | 2019-12-10 | No exploit published | No public exploit | In Ktor through 1.2.6, the client resends data from the HTTP Authorization header to a redirect location. |
| CVE-2019-12737 | Medium | 2019-10-02 | Not applicable | No public exploit | UserHashedTableAuth in JetBrains Ktor framework before 1.2.0-rc uses a One-Way Hash with a Predictable Salt for storing user credentials. |
| CVE-2019-12736 | Critical | 2019-10-02 | Not applicable | No public exploit | JetBrains Ktor framework before 1.2.0-rc does not sanitize the username provided by the user for the LDAP protocol, leading to command injection. |
| CVE-2019-10102 | High | 2019-07-03 | Not applicable | No public exploit | JetBrains Ktor framework (created using the Kotlin IDE template) versions before 1.1.0 were resolving artifacts using an http connection during the build process, potentially allowing an MITM attack. This issue was fixed in Kotlin plugin version 1.3.30. |