Assembla Auth Plugin on Jenkins Configuration File config.xml Credentials credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Assembla Auth Plugin on Jenkins and classified as problematic. This affects an unknown function of the file config.xml of the component Configuration File. The manipulation leads to credentials management (Credentials). This vulnerability is documented as CVE-2019-10280. The attack needs to be performed locally. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Assembla Auth Plugin on Jenkins (Jenkins Plugin) (the affected version unknown). This issue affects an unknown part of the file config.xml of the component Configuration File. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). Using CWE to declare the problem leads to CWE-255. Impacted is confidentiality. The summary by CVE is:
Jenkins Assembla Auth Plugin stores credentials unencrypted in the global config.xml configuration file on the Jenkins master where they can be viewed by users with access to the master file system.
The bug was discovered 04/03/2019. The weakness was released 04/04/2019 (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2019-10280 since 03/29/2019. Attacking locally is a requirement. A simple authentication is necessary for exploitation. 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: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-132981. Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Name
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
03/29/2019 🔍04/03/2019 🔍
04/04/2019 🔍
04/05/2019 🔍
08/25/2023 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-10280 (🔍)
GCVE (CVE): GCVE-0-2019-10280
GCVE (VulDB): GCVE-100-133031
SecurityFocus: 107790
See also: 🔍
Entry
Created: 04/05/2019 08:57Updated: 08/25/2023 14:54
Changes: 04/05/2019 08:57 (57), 06/23/2020 11:31 (3), 08/25/2023 14:54 (3)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.