Tribe29 Checkmk Appliance up to 1.6.3 Log File get request method with sensitive query strings

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.
4.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Tribe29 Checkmk Appliance up to 1.6.3. It has been classified as problematic. The affected element is an unknown function of the component Log File Handler. Performing a manipulation results in use of get request method with sensitive query strings. This vulnerability is cataloged as CVE-2023-22307. The attack must be initiated from a local position. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Tribe29 Checkmk Appliance up to 1.6.3. This affects an unknown code block of the component Log File Handler. The manipulation with an unknown input leads to a use of get request method with sensitive query strings vulnerability. CWE is classifying the issue as CWE-598. The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. This is going to have an impact on confidentiality. The summary by CVE is:

Sensitive data exposure in Webconf in Tribe29 Checkmk Appliance before 1.6.4 allows local attacker to retrieve passwords via reading log files.

The weakness was shared 04/18/2023. The advisory is shared at checkmk.com. This vulnerability is uniquely identified as CVE-2023-22307 since 01/18/2023. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.6.4 eliminates this vulnerability.

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

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.3

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.5
CNA Vector (Tribe29 GmbH): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Use of get request method with sensitive query strings
CWE: CWE-598
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Checkmk Appliance 1.6.4

Timelineinfo

01/18/2023 🔍
04/18/2023 +89 days 🔍
04/18/2023 +0 days 🔍
04/18/2023 +0 days 🔍

Sourcesinfo

Advisory: checkmk.com
Status: Confirmed

CVE: CVE-2023-22307 (🔍)
GCVE (CVE): GCVE-0-2023-22307
GCVE (VulDB): GCVE-100-226749

Entryinfo

Created: 04/18/2023 23:25
Changes: 04/18/2023 23:25 (49)
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.

Might our Artificial Intelligence support you?

Check our Alexa App!