Jira Issue Updater Plugin on Jenkins config.xml Credentials credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Jira Issue Updater Plugin on Jenkins. This affects an unknown part of the file config.xml. Performing a manipulation results in credentials management (Credentials). This vulnerability is identified as CVE-2019-1003054. The attack is only possible with local access. There is not any exploit available.
Details
A vulnerability was found in Jira Issue Updater Plugin on Jenkins (Jenkins Plugin) (affected version not known). It has been classified as problematic. This affects some unknown functionality of the file config.xml. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:
Jenkins Jira Issue Updater Plugin stores credentials 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 bug was discovered 04/03/2019. The weakness was released 04/04/2019 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2019-1003054 since 04/03/2019. An attack has to be approached locally. A authentication is required for 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 1 days. During that time the estimated underground price was around $0-$5k. 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.
Entries connected to this vulnerability are available at VDB-132978, VDB-132979, VDB-132980 and VDB-132982. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.1
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: CredentialsClass: Credentials management / Credentials
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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
04/03/2019 🔍04/03/2019 🔍
04/04/2019 🔍
04/05/2019 🔍
08/25/2023 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-1003054 (🔍)
GCVE (CVE): GCVE-0-2019-1003054
GCVE (VulDB): GCVE-100-132981
SecurityFocus: 107790
See also: 🔍
Entry
Created: 04/05/2019 07:10Updated: 08/25/2023 10:52
Changes: 04/05/2019 07:10 (56), 06/23/2020 06:52 (3), 08/25/2023 10:52 (3)
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.