Ktor
by Jetbrains
Source repositories
CVEs (18)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2019-12736 | Cri | 0.64 | 9.8 | 0.02 | Oct 2, 2019 | 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-2023-45612 | Hig | 0.56 | 8.6 | 0.01 | Oct 9, 2023 | In JetBrains Ktor before 2.3.5 default configuration of ContentNegotiation with XML format was vulnerable to XXE | ||
| CVE-2022-48476 | Hig | 0.49 | 7.5 | 0.01 | Apr 24, 2023 | In JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible | ||
| CVE-2021-43203 | Hig | 0.49 | 7.5 | 0.01 | Nov 9, 2021 | In JetBrains Ktor before 1.6.4, nonce verification during the OAuth2 authentication process is implemented improperly. | ||
| CVE-2019-10102 | Hig | 0.46 | 8.1 | 0.01 | Jul 3, 2019 | 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. | ||
| CVE-2023-45613 | Med | 0.44 | 6.8 | 0.00 | Oct 9, 2023 | In JetBrains Ktor before 2.3.5 server certificates were not verified | ||
| CVE-2020-26129 | Med | 0.42 | 6.5 | 0.01 | Nov 16, 2020 | In JetBrains Ktor before 1.4.1, HTTP request smuggling was possible. | ||
| CVE-2021-25762 | Med | 0.35 | 5.3 | 0.01 | Feb 3, 2021 | In JetBrains Ktor before 1.4.3, HTTP Request Smuggling was possible. | ||
| CVE-2025-29904 | Med | 0.34 | 5.3 | 0.00 | Mar 12, 2025 | In JetBrains Ktor before 3.1.1 an HTTP Request Smuggling was possible | ||
| CVE-2021-25763 | Med | 0.34 | 5.3 | 0.01 | Feb 3, 2021 | In JetBrains Ktor before 1.4.2, weak cipher suites were enabled by default. | ||
| CVE-2021-25761 | Med | 0.34 | 5.3 | 0.01 | Feb 3, 2021 | In JetBrains Ktor before 1.5.0, a birthday attack on SessionStorage key was possible. | ||
| CVE-2024-49580 | Med | 0.27 | 5.3 | 0.00 | Oct 17, 2024 | In JetBrains Ktor before 2.3.13 improper caching in HttpCache Plugin could lead to response information disclosure | ||
| CVE-2022-38180 | Med | 0.27 | 5.3 | 0.01 | Aug 12, 2022 | In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases | ||
| CVE-2022-38179 | Med | 0.24 | 4.7 | 0.00 | Aug 12, 2022 | JetBrains Ktor before 2.1.0 was vulnerable to the Reflect File Download attack | ||
| CVE-2023-34339 | Low | 0.21 | 3.3 | 0.00 | Jun 1, 2023 | In JetBrains Ktor before 2.3.1 headers containing authentication data could be added to the exception's message | ||
| CVE-2022-29930 | Hig | 0.00 | 8.7 | 0.01 | May 12, 2022 | 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 | 0.00 | 3.3 | 0.01 | Apr 11, 2022 | In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations | ||
| CVE-2019-19389 | Med | 0.00 | 5.4 | 0.01 | Dec 26, 2019 | JetBrains Ktor framework before version 1.2.6 was vulnerable to HTTP Response Splitting. |
- risk 0.64cvss 9.8epss 0.02
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.
- risk 0.56cvss 8.6epss 0.01
In JetBrains Ktor before 2.3.5 default configuration of ContentNegotiation with XML format was vulnerable to XXE
- risk 0.49cvss 7.5epss 0.01
In JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible
- risk 0.49cvss 7.5epss 0.01
In JetBrains Ktor before 1.6.4, nonce verification during the OAuth2 authentication process is implemented improperly.
- risk 0.46cvss 8.1epss 0.01
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.
- risk 0.44cvss 6.8epss 0.00
In JetBrains Ktor before 2.3.5 server certificates were not verified
- risk 0.42cvss 6.5epss 0.01
In JetBrains Ktor before 1.4.1, HTTP request smuggling was possible.
- risk 0.35cvss 5.3epss 0.01
In JetBrains Ktor before 1.4.3, HTTP Request Smuggling was possible.
- risk 0.34cvss 5.3epss 0.00
In JetBrains Ktor before 3.1.1 an HTTP Request Smuggling was possible
- risk 0.34cvss 5.3epss 0.01
In JetBrains Ktor before 1.4.2, weak cipher suites were enabled by default.
- risk 0.34cvss 5.3epss 0.01
In JetBrains Ktor before 1.5.0, a birthday attack on SessionStorage key was possible.
- risk 0.27cvss 5.3epss 0.00
In JetBrains Ktor before 2.3.13 improper caching in HttpCache Plugin could lead to response information disclosure
- risk 0.27cvss 5.3epss 0.01
In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases
- risk 0.24cvss 4.7epss 0.00
JetBrains Ktor before 2.1.0 was vulnerable to the Reflect File Download attack
- risk 0.21cvss 3.3epss 0.00
In JetBrains Ktor before 2.3.1 headers containing authentication data could be added to the exception's message
- risk 0.00cvss 8.7epss 0.01
SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. The issue was fixed in Ktor version 2.0.1.
- risk 0.00cvss 3.3epss 0.01
In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations
- risk 0.00cvss 5.4epss 0.01
JetBrains Ktor framework before version 1.2.6 was vulnerable to HTTP Response Splitting.