Harvest SCM Plugin up to 0.5.1 on Jenkins config.xml Password credentials storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Harvest SCM Plugin up to 0.5.1 on Jenkins. This issue affects some unknown processing of the file config.xml. The manipulation leads to credentials storage (Password). This vulnerability is uniquely identified as CVE-2020-2131. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in Harvest SCM Plugin up to 0.5.1 on Jenkins (Supply Chain Management Software). This issue affects an unknown code of the file config.xml. The manipulation with an unknown input leads to a credentials storage vulnerability (Password). Using CWE to declare the problem leads to CWE-256. Storing a password in plaintext may result in a system compromise. Impacted is confidentiality. The summary by CVE is:
Jenkins Harvest SCM Plugin 0.5.1 and earlier stores passwords unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.
The weakness was disclosed 02/12/2020 (oss-sec). The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2020-2131 since 12/05/2019. The attack may be initiated remotely. A simple authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
By approaching the search of inurl:config.xml it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-150055, VDB-150056, VDB-150057 and VDB-150058 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: PasswordClass: Credentials storage / Password
CWE: CWE-256 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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
12/05/2019 🔍02/12/2020 🔍
02/13/2020 🔍
02/13/2020 🔍
Sources
Advisory: openwall.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-2131 (🔍)
GCVE (CVE): GCVE-0-2020-2131
GCVE (VulDB): GCVE-100-150077
See also: 🔍
Entry
Created: 02/13/2020 08:23Updated: 02/13/2020 08:28
Changes: 02/13/2020 08:23 (40), 02/13/2020 08:28 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.