Elasticsearch Query Plugin up to 1.2 on Jenkins Configuration File credentials storage

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.0$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Elasticsearch Query Plugin up to 1.2 on Jenkins. This issue affects some unknown processing of the component Configuration File Handler. This manipulation causes credentials storage. This vulnerability appears as CVE-2022-34807. There is no available exploit.

Detailsinfo

A vulnerability has been found in Elasticsearch Query Plugin up to 1.2 on Jenkins (Jenkins Plugin) and classified as problematic. Affected by this vulnerability is an unknown code of the component Configuration File Handler. The manipulation with an unknown input leads to a credentials storage vulnerability. The CWE definition for the vulnerability is CWE-256. Storing a password in plaintext may result in a system compromise. As an impact it is known to affect confidentiality. The summary by CVE is:

Jenkins Elasticsearch Query Plugin 1.2 and earlier stores a password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.

The weakness was presented 07/01/2022. The advisory is shared at jenkins.io. This vulnerability is known as CVE-2022-34807 since 06/29/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

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.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 5.0

VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Credentials storage
CWE: CWE-256 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

06/29/2022 🔍
07/01/2022 +2 days 🔍
07/01/2022 +0 days 🔍
07/17/2022 +16 days 🔍

Sourcesinfo

Advisory: jenkins.io
Status: Confirmed

CVE: CVE-2022-34807 (🔍)
GCVE (CVE): GCVE-0-2022-34807
GCVE (VulDB): GCVE-100-203053

Entryinfo

Created: 07/01/2022 13:23
Updated: 07/17/2022 13:15
Changes: 07/01/2022 13:23 (40), 07/17/2022 13:15 (18)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!