JetBrains IntelliJ IDEA Gradle Artifact Resolver HTTP input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in JetBrains IntelliJ IDEA. This affects an unknown part of the component Gradle Artifact Resolver. Such manipulation leads to input validation (HTTP). This vulnerability is uniquely identified as CVE-2019-10103. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in JetBrains IntelliJ IDEA (unknown version) and classified as critical. Affected by this issue is an unknown code block of the component Gradle Artifact Resolver. The manipulation with an unknown input leads to a input validation vulnerability (HTTP). Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was disclosed 07/03/2019 (Website). The advisory is available at blog.jetbrains.com. This vulnerability is handled as CVE-2019-10103 since 03/26/2019. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-137280, VDB-137283, VDB-137287 and VDB-137288 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: HTTPClass: Input validation / HTTP
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/26/2019 🔍07/03/2019 🔍
07/04/2019 🔍
06/30/2020 🔍
Sources
Advisory: blog.jetbrains.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-10103 (🔍)
GCVE (CVE): GCVE-0-2019-10103
GCVE (VulDB): GCVE-100-137282
See also: 🔍
Entry
Created: 07/04/2019 09:59Updated: 06/30/2020 17:23
Changes: 07/04/2019 09:59 (56), 06/30/2020 17:23 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.