CVE-2019-10102
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJetBrains 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe JetBrains Ktor framework project template versions before 1.1.0 were resolving build artifacts over unencrypted HTTP connections during the Gradle/Maven build process. This allowed potential MITM attackers to intercept and inject malicious code into dependencies being downloaded, compromising the software supply chain.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3.30< 1.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Kotlin plugin version in build configurationInspect the build.gradle file for the Kotlin plugin version (e.g., ext.kotlin_version or kotlin("1.x.x") and compare to 1.3.30Affected if Kotlin version is listed and is less than 1.3.30
-
Check Kotlin version in dependenciesLook for the kotlin-stdlib or kotlin-reflect dependency version in build.gradle dependencies blockAffected if Kotlin dependency version is less than 1.3.30
-
Check Ktor dependency versionSearch for ktor dependencies (e.g., ktor-server-core, ktor-server-netty) in build.gradle and note their versionAffected if Ktor version is less than 1.1.0 or not specified with a version 1.1.0 or higher
-
Inspect repository URLs in build filesExamine build.gradle and settings.gradle for repository blocks (mavenCentral, jcenter, maven { url }) and check if URLs use http:// instead of https://Affected if Any repository URL starts with http:// (unencrypted)
-
Check gradle wrapper propertiesInspect gradle/wrapper/gradle-wrapper.properties for repository URLs referencing HTTPAffected if Distribution URL uses http:// instead of https://
A user is affected if they use Kotlin below 1.3.30 or Ktor below 1.1.0, or if any build configuration contains HTTP (unencrypted) URLs for artifact repositories.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.1.01.3.30
Update Kotlin plugin to version 1.3.30 or later and verify all artifact repository URLs in build configurations use HTTPS instead of HTTP.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10102 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data