Security readout for executives and security teams
Plain-English summary
This is a build-time supply-chain risk in JetBrains Ktor projects created from the Kotlin IDE template before Ktor 1.1.0. The template resolved build artifacts over HTTP, so someone able to intercept network traffic could potentially tamper with dependencies during builds.
Executive priority
Treat as a targeted supply-chain hygiene issue. Prioritize environments that build Kotlin/Ktor applications, especially CI systems and developers using untrusted networks.
Technical view
The CVE describes artifact resolution over an unencrypted HTTP connection during the build process for affected Ktor projects. The issue is not described as a runtime web application flaw. JetBrains fixed it in Kotlin plugin 1.3.30.
Likely exposure
Exposure is most likely in developer workstations or CI systems building Ktor projects generated by the affected Kotlin IDE template before the fix.
Exploitation context
The sources do not state active exploitation, and the CVE is not listed as KEV. Practical exploitation would require a network man-in-the-middle position during dependency resolution.
Researcher notes
The public bundle provides limited affected-product metadata and no CVSS vector. Analysis should remain scoped to Ktor projects created from the affected template and the documented Kotlin plugin fix.
Mitigation direction
- Update JetBrains Kotlin plugin to version 1.3.30 or later.
- Check JetBrains guidance for any additional remediation details.
- Audit build files for HTTP artifact repositories or dependency sources.
- Prefer HTTPS-only artifact resolution in developer and CI builds.
Validation and detection
- Identify Ktor projects generated from older Kotlin IDE templates.
- Review CI and developer build logs for HTTP artifact downloads.
- Check Kotlin plugin versions on developer systems using the template.
- Confirm build configuration no longer references HTTP repositories.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-10102 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.