Performance Publisher Plugin up to 4.8.0.143 on Jenkins Controller File System config.xml credentials storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Performance Publisher Plugin up to 4.8.0.143 on Jenkins. The affected element is an unknown function of the file config.xml of the component Controller File System Handler. The manipulation leads to credentials storage. This vulnerability is referenced as CVE-2022-45392. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in Performance Publisher Plugin up to 4.8.0.143 on Jenkins (Jenkins Plugin). This issue affects an unknown functionality of the file config.xml of the component Controller File System Handler. The manipulation with an unknown input leads to a credentials storage vulnerability. 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 NS-ND Integration Performance Publisher Plugin 4.8.0.143 and earlier stores passwords unencrypted in job config.xml files on the Jenkins controller where they can be viewed by attackers with Extended Read permission, or access to the Jenkins controller file system.
The weakness was published 11/15/2022. The advisory is shared at jenkins.io. The identification of this vulnerability is CVE-2022-45392 since 11/14/2022. 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.
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: 🔍
Exploiting
Class: Credentials storageCWE: 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
11/14/2022 🔍11/15/2022 🔍
11/15/2022 🔍
12/19/2022 🔍
Sources
Advisory: jenkins.ioStatus: Confirmed
CVE: CVE-2022-45392 (🔍)
GCVE (CVE): GCVE-0-2022-45392
GCVE (VulDB): GCVE-100-213725
Entry
Created: 11/15/2022 22:54Updated: 12/19/2022 07:12
Changes: 11/15/2022 22:54 (40), 12/19/2022 07:12 (12)
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.