Coverity Plugin up to 1.10.0 on Jenkins CIMInstance.java Key credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Coverity Plugin up to 1.10.0 on Jenkins. Impacted is an unknown function of the file CIMInstance.java. The manipulation leads to credentials management (Key). This vulnerability is traded as CVE-2018-1000104. An attack has to be approached locally. There is no exploit available.
Details
A vulnerability was found in Coverity Plugin up to 1.10.0 on Jenkins (Jenkins Plugin) and classified as problematic. This issue affects some unknown processing of the file CIMInstance.java. The manipulation with an unknown input leads to a credentials management vulnerability (Key). Using CWE to declare the problem leads to CWE-255. Impacted is confidentiality. The summary by CVE is:
A plaintext storage of a password vulnerability exists in Jenkins Coverity Plugin 1.10.0 and earlier in CIMInstance.java that allows an attacker with local file system access or control of a Jenkins administrator's web browser (e.g. malicious extension) to retrieve the configured keystore and private key passwords.
The bug was discovered 02/26/2018. The weakness was shared 03/13/2018 (Website). The advisory is shared at jenkins.io. The identification of this vulnerability is CVE-2018-1000104 since 03/13/2018. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 15 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: KeyClass: Credentials management / Key
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
02/26/2018 🔍03/13/2018 🔍
03/13/2018 🔍
03/13/2018 🔍
03/14/2018 🔍
07/16/2020 🔍
Sources
Advisory: jenkins.ioStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-1000104 (🔍)
GCVE (CVE): GCVE-0-2018-1000104
GCVE (VulDB): GCVE-100-114449
Entry
Created: 03/14/2018 07:52Updated: 07/16/2020 17:41
Changes: 03/14/2018 07:52 (59), 07/16/2020 17:41 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.