Security readout for executives and security teams
Plain-English summary
Some IntelliJ IDEA Kotlin template projects could fetch build dependencies over unencrypted HTTP. A network attacker in the right position could tamper with downloaded artifacts. This mainly affects developer build environments and software supply chain integrity, not a directly exposed production service.
Executive priority
Treat this as a developer supply chain hygiene issue. Prioritize teams building legacy Kotlin template projects or working on untrusted networks. Urgency is lower than an internet-facing RCE but meaningful where builds produce production software.
Technical view
JetBrains reported that projects created with the Kotlin (JS Client/JVM Server) IDE Template resolved Gradle artifacts over HTTP. The flaw could enable man-in-the-middle manipulation of dependency retrieval. JetBrains states it was fixed in Kotlin plugin version 1.3.30.
Likely exposure
Exposure is most likely in older IntelliJ IDEA projects generated from the named Kotlin template before Kotlin plugin 1.3.30, especially where Gradle repository URLs still use HTTP. The source bundle does not identify specific affected product versions beyond that plugin fix reference.
Exploitation context
The source describes potential MITM risk but does not cite public exploitation, proof-of-concept activity, or CISA KEV listing. Exploitation would require an attacker able to influence network traffic during dependency resolution.
Researcher notes
The public record lacks CVSS, CWE, precise affected version ranges, and exploit evidence. Analysis should focus on generated Gradle configuration, plugin version history, and whether any surviving repositories use HTTP during artifact resolution.
Mitigation direction
- Upgrade the Kotlin plugin to version 1.3.30 or later.
- Review generated Gradle files for HTTP artifact repositories.
- Replace HTTP dependency repositories with vendor-supported HTTPS endpoints.
- Check JetBrains guidance before applying project-wide dependency changes.
Validation and detection
- Inventory IntelliJ IDEA Kotlin JS Client/JVM Server template projects.
- Inspect Gradle repository configuration for plain HTTP URLs.
- Confirm developer IDEs use Kotlin plugin 1.3.30 or later.
- Review build logs for dependency downloads from HTTP endpoints.
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-10103 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.