{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10103 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10103 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10103 is a high-severity vulnerability in n/a, published on 3 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10103 and fix it if it is affected.\n\nWhat it is: CVE-2019-10103 is a high-severity vulnerability in n/a, published on 3 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10103 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-10103/ (Markdown: https://insights.sbomify.com/CVE-2019-10103/index.md)","id":"CVE-2019-10103","markdown":"https://insights.sbomify.com/CVE-2019-10103/index.md","name":"CVE-2019-10103","record":{"aliases":["GHSA-8fr9-3mxv-p3vf","UBUNTU-CVE-2019-10103"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IntelliJ IDEA Kotlin plugin","requires_auth":"none","summary":"Attackers can intercept Gradle artifact downloads via MITM due to insecure HTTP usage in IntelliJ IDEA Kotlin project templates.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kotlin","vendor":"jetbrains"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"JetBrains IntelliJ IDEA projects created using the Kotlin (JS Client/JVM Server) IDE Template were resolving Gradle artifacts using an http connection, potentially allowing an MITM attack. This issue, which was fixed in Kotlin plugin version 1.3.30, is similar to CVE-2019-10101.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Other in n/a","id":"CVE-2019-10103","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Misconfiguration in n/a","id":"CVE-2019-10104"},"packages":[],"prev":{"headline":"Supply chain in n/a","id":"CVE-2019-10102"},"products":["n/a"],"published":"2019-07-03","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-15824","kev_date_added":null,"published":"2020-08-08"},{"cvss_score":8.1,"headline":"Other in n/a","id":"CVE-2019-10101","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":8.1,"headline":"Supply chain in n/a","id":"CVE-2019-10102","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":6.7,"headline":"JetBrains Kotlin: Unsafe Deserialization in Kotlin Build Cache Enables Code Execution","id":"CVE-2026-53914","kev_date_added":null,"published":"2026-06-26"},{"cvss_score":5.3,"headline":"Improper Locking in JetBrains Kotlin","id":"CVE-2022-24329","kev_date_added":null,"published":"2022-02-25"},{"cvss_score":5.3,"headline":"Incorrect Default Permissions in JetBrains Kotlin","id":"CVE-2020-29582","kev_date_added":null,"published":"2021-02-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can intercept Gradle artifact downloads via MITM due to insecure HTTP usage in IntelliJ IDEA Kotlin project templates.","url":"https://insights.sbomify.com/CVE-2019-10103/"}