Ktor CVE-2022-38179

In Ktor through 1.2.6, the client resends data from the HTTP Authorization header to a redirect location. Rated medium s

In JetBrains Ktor before 2.3.5 default configuration of ContentNegotiation with XML format was vulnerable to XXE. Rated

JetBrains Ktor framework before 1.2.0-rc does not sanitize the username provided by the user for the LDAP protocol, lead

JetBrains Ktor framework before version 1.2.6 was vulnerable to HTTP Response Splitting. Rated medium severity (CVSS 5.4

In JetBrains Ktor before 2.3.5 server certificates were not verified. Rated critical severity (CVSS 9.1), this vulnerabi

JetBrains Ktor framework (created using the Kotlin IDE template) versions before 1.1.0 were resolving artifacts using an

In JetBrains Ktor before 1.6.4, nonce verification during the OAuth2 authentication process is implemented improperly. R

In Ktor before 1.3.0, request smuggling is possible when running behind a proxy that doesn't handle Content-Length and T

In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases. Rated medium severity

In JetBrains Ktor before 1.4.1, HTTP request smuggling was possible. Rated medium severity (CVSS 6.5), this vulnerabilit

In JetBrains Ktor before 3.1.1 an HTTP Request Smuggling was possible. Rated medium severity (CVSS 5.3), this vulnerabil

In JetBrains Ktor before 2.3.13 improper caching in HttpCache Plugin could lead to response information disclosure. Rate