End of life: 11/27/2024, Latest version: 2.0.21
End of life: 11/27/2024, Latest version: 2.0.21
End of life: 5/21/2024, Latest version: 1.9.25
End of life: 5/21/2024, Latest version: 1.9.25
End of life: 7/6/2023, Latest version: 1.8.22
End of life: 7/6/2023, Latest version: 1.8.22
End of life: 12/28/2022, Latest version: 1.7.22
End of life: 12/28/2022, Latest version: 1.7.22
In JetBrains Kotlin before 1.6.0, it was not possible to lock dependencies for Multiplatform Gradle Projects.
End of life: 6/9/2022, Latest version: 1.6.21
End of life: 6/9/2022, Latest version: 1.6.21
End of life: 11/29/2021, Latest version: 1.5.32
End of life: 11/29/2021, Latest version: 1.5.32
End of life: 4/26/2021, Latest version: 1.4.32
End of life: 4/26/2021, Latest version: 1.4.32
In JetBrains Kotlin from 1.4-M1 to 1.4-RC (as Kotlin 1.3.7x is not affected by the issue. Fixed version is 1.4.0) there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.
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.
JetBrains Kotlin versions before 1.3.30 were resolving artifacts using an http connection during the build process, potentially allowing an MITM attack.
JetBrains IntelliJ IDEA projects created using the Kotlin (JS Client/JVM Server) IDE Template were resolving Gradle artifacts using an http connection, potentially allowing an MITM attack. This issue, which was fixed in Kotlin plugin version 1.3.30, is similar to CVE-2019-10101.
End of life: 8/14/2020, Latest version: 1.3.72
End of life: 8/14/2020, Latest version: 1.3.72