CPE Details
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
CPE Name: cpe:2.3:a:jetbrains:ktor:0.9.3:-:*:*:*:*:*:*
Informations
Vendor
jetbrainsProduct
ktorVersion
0.9.3Update
-Related CVE
| CVE ID | Published | Description | Score | Severity |
|---|---|---|---|---|
| In JetBrains Ktor before 2.3.13 improper caching in HttpCache Plugin could lead to response information disclosure | 5.3 |
Medium |
||
| In JetBrains Ktor before 2.3.5 server certificates were not verified | 9.1 |
Critical |
||
| In JetBrains Ktor before 2.3.5 default configuration of ContentNegotiation with XML format was vulnerable to XXE | 9.8 |
Critical |
||
| In JetBrains Ktor before 2.3.1 headers containing authentication data could be added to the exception's message | 3.3 |
Low |
||
| In JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible | 7.5 |
High |
||
| In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases | 6.5 |
Medium |
||
| JetBrains Ktor before 2.1.0 was vulnerable to the Reflect File Download attack | 6.1 |
Medium |
||
| In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations | 3.3 |
Low |
||
| In JetBrains Ktor before 1.6.4, nonce verification during the OAuth2 authentication process is implemented improperly. | 7.5 |
High |
||
| In JetBrains Ktor before 1.4.3, HTTP Request Smuggling was possible. | 5.3 |
Medium |
||
| In JetBrains Ktor before 1.4.2, weak cipher suites were enabled by default. | 5.3 |
Medium |
||
| In JetBrains Ktor before 1.5.0, a birthday attack on SessionStorage key was possible. | 5.3 |
Medium |
||
| In JetBrains Ktor before 1.4.1, HTTP request smuggling was possible. | 6.5 |
Medium |
||
| 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. | 7.5 |
High |
||
| JetBrains Ktor framework before version 1.2.6 was vulnerable to HTTP Response Splitting. | 5.4 |
Medium |
||
| In Ktor through 1.2.6, the client resends data from the HTTP Authorization header to a redirect location. | 6.1 |
Medium |
||
| 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. | 9.8 |
Critical |
||
| UserHashedTableAuth in JetBrains Ktor framework before 1.2.0-rc uses a One-Way Hash with a Predictable Salt for storing user credentials. | 5.3 |
Medium |
||
| 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. | 8.1 |
High |
The information presented on CVE Find originates from several carefully selected reference sources. CVE data is provided by MITRE Corporation and the National Vulnerability Database (NVD). The Known Exploited Vulnerabilities (KEV) catalog is sourced from the Cybersecurity and Infrastructure Security Agency (CISA), while EPSS scores come from FIRST.org. Additionally, data regarding software weaknesses (CWE) and common attack patterns (CAPEC) is maintained by MITRE Corporation, and information on hardware and software configurations (CPE) is provided by the NVD.