JetBrains Ktor Code Issue Vulnerability

JetBrains Ktor framework is a web application framework from the Czech company JetBrains. A code issue vulnerability exists in JetBrains Ktor versions prior to 2.3.5 that stems from an XML External Entity Injection XXE vulnerability in the default configuration of ContentNegotiation...

JetBrains Ktor Trust Management Issues Vulnerability

The JetBrains Ktor framework is a web application framework from the Czech company JetBrains. A trust management issue vulnerability exists in JetBrains Ktor versions prior to 2.3.5, which stems from a failure to validate server certificates, resulting in a trust management issue vulnerability...

CVE-2023-34339

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

Authentication flaw

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

CVE-2023-34339

CVE-2023-34339 affects JetBrains Ktor prior to 2.3.1. The issue is that headers containing authentication data could be added to exception messages, enabling potential exposure of sensitive information. Multiple connected sources (Red Hat, Veracode, CVE lists) confirm the same impact and scope. T...

CVE-2023-34339

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

CVE-2023-34339

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

CVE-2023-34339

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

PT-2023-24824 · Jetbrains · Jetbrains Ktor

Name of the Vulnerable Software and Affected Versions: JetBrains Ktor versions prior to 2.3.1 Description: The issue allows headers containing authentication data to be added to the exception's message. This could potentially expose sensitive information. Recommendations: For versions prior to...

JetBrains Ktor framework 安全漏洞

JetBrains Ktor framework is a web application framework from the Czech company JetBrains. A security vulnerability exists in JetBrains Ktor framework versions prior to 2.3.1, which stems from a header for authentication data that can be added to an exception message...

CVE-2022-48476

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

Path traversal

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

CVE-2022-48476

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

CVE-2022-48476

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

CVE-2022-48476

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

CVE-2022-48476

In JetBrains Ktor, prior to version 2.3.0, there is a path traversal vulnerability in the resolveResource method. Affected software is Ktor (JetBrains’ framework); root cause per sources is a path traversal flaw in resolveResource. The CVE is linked across multiple feeds (NVD/Red Hat/OSV/etc.). I...

PT-2023-15809 · Jetbrains · Jetbrains Ktor

Name of the Vulnerable Software and Affected Versions: JetBrains Ktor versions prior to 2.3.0 Description: The issue allows path traversal in the resolveResource method. Recommendations: For versions prior to 2.3.0, update to version 2.3.0 or later to resolve the issue. As a temporary workaround,...

JetBrains Ktor framework 路径遍历漏洞

JetBrains Ktor framework is a web application framework from the Czech company JetBrains. A security vulnerability exists in JetBrains Ktor framework versions prior to 2.3.0, which stems from the discovery of a contained path traversal vulnerability in the resolveResource method...

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

JetBrains Ktor before 2.1.0 was vulnerable to a Reflect File Download attack...

JetBrain Ktor before 2.1.0 vulnerable to selection of wrong authentication provider

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