Conjur Secrets Plugin up to 1.0.9 on Jenkins Credentials protection mechanism
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Conjur Secrets Plugin up to 1.0.9 on Jenkins and classified as problematic. This issue affects some unknown processing of the component Credentials Handler. This manipulation causes protection mechanism. The identification of this vulnerability is CVE-2022-23117. There is no exploit available.
Details
A vulnerability was found in Conjur Secrets Plugin up to 1.0.9 on Jenkins (Jenkins Plugin). It has been declared as problematic. Affected by this vulnerability is an unknown part of the component Credentials Handler. The manipulation with an unknown input leads to a protection mechanism vulnerability. The CWE definition for the vulnerability is CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. As an impact it is known to affect confidentiality.
The weakness was shared 01/13/2022. The advisory is shared at jenkins.io. This vulnerability is known as CVE-2022-23117 since 01/11/2022. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Protection mechanismCWE: CWE-693
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
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
01/11/2022 🔍01/13/2022 🔍
01/13/2022 🔍
01/16/2022 🔍
Sources
Advisory: jenkins.ioStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2022-23117 (🔍)
GCVE (CVE): GCVE-0-2022-23117
GCVE (VulDB): GCVE-100-190249
Entry
Created: 01/13/2022 07:34Updated: 01/16/2022 07:23
Changes: 01/13/2022 07:34 (37), 01/16/2022 07:23 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.