CVE-2019-19389

JetBrains Ktor framework before version 1.2.6 was vulnerable to HTTP Response Splitting...

CVE-2019-19389

CVE-2019-19389 affects JetBrains Ktor framework prior to version 1.2.6 and is described as an HTTP Response Splitting vulnerability. Red Hat and CNVD entries corroborate the same flaw, with JetBrains’ Q4 2019 security bulletin listing Ktor as affected and noting the issue is resolved in version 1...

CVE-2019-19703

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

CVE-2019-19703

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

Authorization

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

CVE-2019-19703

The CVE-2019-19703 entry concerns the Ktor framework (through version 1.2.6) where the client resends data from the HTTP Authorization header to a redirect location, creating an open-redirect risk. Connected sources (Red Hat, GitHub advisories, OSV, and CVE lists) consistently describe this Issue...

CVE-2019-19703

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

Unspecified vulnerability in JetBrains Ktor framework

JetBrains Ktor framework is a Web application framework from the Czech company JetBrains. An unspecified vulnerability exists in JetBrains Ktor framework. An attacker can exploit this vulnerability to obtain sensitive information...

JetBrains Ktor framework input validation error vulnerability

JetBrains Ktor framework is a Web application framework from the Czech company JetBrains. An input validation error vulnerability exists in JetBrains Ktor framework. An attacker could exploit this vulnerability to execute commands...

CVE-2019-12737

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

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-12736

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-12737

UserHashedTableAuth in JetBrains Ktor framework before 1.2.0-rc uses a One-Way Hash with a Predictable Salt for storing user credentials...

Command injection

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-12736

CVE-2019-12736 affects JetBrains Kotlin Ktor framework prior to 1.2.0-rc, where the LDAP username is not sanitized, enabling command injection. Impact described as significant; next steps require upgrading to 1.2.0-rc or 1.2.0 (fixes included). If exploitation details are not provided in the sour...

CVE-2019-12736

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-12737

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-12737

CVE-2019-12737 affects JetBrains Kotlin Ktor framework prior to 1.2.0-rc, where UserHashedTableAuth stores credentials using a one-way hash with a predictable salt. This weakens credential protection and aligns with the NVD CVSS 2.0/3.1 scores (base ~5.0–5.3, MEDIUM). The issue is documented acro...

CVE-2019-10102

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-2019-10102

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...