Azure PublisherSettings Credentials Plugin up to 1.2 on Jenkins credentials.xml credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Azure PublisherSettings Credentials Plugin up to 1.2 on Jenkins. Affected by this issue is some unknown functionality of the file credentials.xml. Performing a manipulation results in credentials management (Credentials). This vulnerability is reported as CVE-2019-10303. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Azure PublisherSettings Credentials Plugin up to 1.2 on Jenkins (Jenkins Plugin). It has been classified as problematic. This affects an unknown functionality of the file credentials.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 Azure PublisherSettings Credentials Plugin 1.2 and earlier stored credentials unencrypted in the credentials.xml file on the Jenkins master where they could be viewed by users with access to the master file system.
The bug was discovered 04/17/2019. The weakness was disclosed 04/18/2019 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2019-10303 since 03/29/2019. It is possible to initiate the attack remotely. The successful exploitation needs a authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
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:credentials.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-133824, VDB-133825, VDB-133826 and VDB-133828 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: 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
03/29/2019 🔍04/17/2019 🔍
04/18/2019 🔍
04/19/2019 🔍
09/04/2023 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-10303 (🔍)
GCVE (CVE): GCVE-0-2019-10303
GCVE (VulDB): GCVE-100-133827
SecurityFocus: 108045
See also: 🔍
Entry
Created: 04/19/2019 06:57Updated: 09/04/2023 17:20
Changes: 04/19/2019 06:57 (57), 05/30/2020 20:44 (4), 09/04/2023 17:20 (3)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.