Black Duck Hub Plugin up to 4.0.0 on Jenkins PostBuildScanDescriptor.java Credentials information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Black Duck Hub Plugin up to 4.0.0 on Jenkins. This issue affects some unknown processing of the file PostBuildScanDescriptor.java. The manipulation results in information disclosure (Credentials). This vulnerability is known as CVE-2018-1000190. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability classified as problematic has been found in Black Duck Hub Plugin up to 4.0.0 on Jenkins (Jenkins Plugin). Affected is an unknown functionality of the file PostBuildScanDescriptor.java. The manipulation with an unknown input leads to a information disclosure vulnerability (Credentials). CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:
A exposure of sensitive information vulnerability exists in Jenkins Black Duck Hub Plugin 4.0.0 and older in PostBuildScanDescriptor.java that allows attackers with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
The bug was discovered 06/05/2018. The weakness was published 06/05/2018 (Website). The advisory is shared for download at jenkins.io. This vulnerability is traded as CVE-2018-1000190 since 06/05/2018. The exploitability is told to be easy. It is possible to launch the attack remotely. The successful exploitation needs a authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: CredentialsClass: Information disclosure / Credentials
CWE: CWE-200 / CWE-284 / CWE-266
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: 🔍
Timeline
06/05/2018 🔍06/05/2018 🔍
06/05/2018 🔍
06/05/2018 🔍
06/06/2018 🔍
07/16/2020 🔍
Sources
Advisory: jenkins.ioStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-1000190 (🔍)
GCVE (CVE): GCVE-0-2018-1000190
GCVE (VulDB): GCVE-100-118980
Entry
Created: 06/06/2018 10:19Updated: 07/16/2020 20:36
Changes: 06/06/2018 10:19 (57), 07/16/2020 20:36 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.