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.
8.1CVSS
7.9AI Score
0.002EPSS
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.
9.8CVSS
9.7AI Score
0.005EPSS
UserHashedTableAuth in JetBrains Ktor framework before 1.2.0-rc uses a One-Way Hash with a Predictable Salt for storing user credentials.
5.3CVSS
5.2AI Score
0.001EPSS
JetBrains Ktor framework before version 1.2.6 was vulnerable to HTTP Response Splitting.
5.4CVSS
5.4AI Score
0.001EPSS
In Ktor through 1.2.6, the client resends data from the HTTP Authorization header to a redirect location.
6.1CVSS
6.1AI Score
0.001EPSS
6.5CVSS
6.5AI Score
0.001EPSS
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.
7.5CVSS
7.4AI Score
0.001EPSS
In JetBrains Ktor before 1.5.0, a birthday attack on SessionStorage key was possible.
5.3CVSS
5.2AI Score
0.001EPSS
5.3CVSS
5.3AI Score
0.001EPSS
5.3CVSS
5.3AI Score
0.001EPSS
In JetBrains Ktor before 1.6.4, nonce verification during the OAuth2 authentication process is implemented improperly.
7.5CVSS
7.7AI Score
0.001EPSS
In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations
3.3CVSS
4.1AI Score
0.001EPSS
SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. The issue was fixed in Ktor version 2.0.1.
8.7CVSS
5.1AI Score
0.001EPSS
6.1CVSS
6.2AI Score
0.001EPSS
In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases
6.5CVSS
6.5AI Score
0.002EPSS
In JetBrains Ktor before 2.3.0 path traversal in the resolveResource method was possible
7.5CVSS
7.5AI Score
0.001EPSS
In JetBrains Ktor before 2.3.1 headers containing authentication data could be added to the exception's message
3.3CVSS
4.2AI Score
0.0004EPSS
In JetBrains Ktor before 2.3.5 default configuration of ContentNegotiation with XML format was vulnerable to XXE
9.8CVSS
9.4AI Score
0.001EPSS
9.1CVSS
9.2AI Score
0.001EPSS