Missing Domain Attribute Validation Allows Cookie Injection in JetBrains Ktor

In JetBrains Ktor before 3.6.1 missing Domain attribute validation in client cookie storage allowed cookie injection

Ktor CIO Engine HTTP Request Smuggling Vulnerability

In JetBrains Ktor before 3.6.1 hTTP request smuggling was possible in the CIO engine

Session Forgery via Tampered Encrypted Cookies in JetBrains Ktor

In JetBrains Ktor before 3.6.1 session forgery was possible via tampered encrypted session cookies

Ktor WebSocket Decompression Denial of Service Vulnerability

In JetBrains Ktor before 3.4.1 potential DoS attack via WebSocket decompression was possible

In JetBrains Ktor before 3.1.1 an HTTP Request Smuggling was possible

In JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible

In JetBrains Ktor before 2.3.1 headers containing authentication data could be added to the exception's message

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

In JetBrains Ktor before 2.3.5 server certificates were not verified

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

In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases

JetBrains Ktor before 2.1.0 was vulnerable to the Reflect File Download attack

SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. The issue was fixed in Ktor version 2.0.1.

In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations

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

In JetBrains Ktor before 1.4.2, weak cipher suites were enabled by default.

In JetBrains Ktor before 1.4.3, HTTP Request Smuggling was possible.

In JetBrains Ktor before 1.5.0, a birthday attack on SessionStorage key was possible.

Request smuggling is possible in Ktor when both chunked TE and content length specified

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.

In JetBrains Ktor before 1.4.1, HTTP request smuggling was possible.