Checkmk up to 2.0.0p39/2.1.0p36/2.2.0p14 Availability Timeline delimiter

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

Summaryinfo

A vulnerability has been found in Checkmk up to 2.0.0p39/2.1.0p36/2.2.0p14 and classified as critical. This issue affects some unknown processing of the component Availability Timeline. Performing a manipulation results in delimiter. This vulnerability is reported as CVE-2023-6156. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical has been found in Checkmk up to 2.0.0p39/2.1.0p36/2.2.0p14. This affects an unknown part of the component Availability Timeline. The manipulation with an unknown input leads to a delimiter vulnerability. CWE is classifying the issue as CWE-140. The product does not neutralize or incorrectly neutralizes delimiters. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Improper neutralization of livestatus command delimiters in the availability timeline in Checkmk <= 2.0.0p39, < 2.1.0p37, and < 2.2.0p15 allows arbitrary livestatus command execution for authorized users.

The weakness was disclosed 11/22/2023. The advisory is shared at checkmk.com. This vulnerability is uniquely identified as CVE-2023-6156 since 11/15/2023. Neither technical details nor an exploit are publicly available.

Upgrading to version 2.1.0p37 or 2.2.0p15 eliminates this vulnerability.

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

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.5

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CNA Base Score: 7.6
CNA Vector (Checkmk GmbH): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Delimiter
CWE: CWE-140 / CWE-20
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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Checkmk 2.1.0p37/2.2.0p15

Timelineinfo

11/15/2023 🔍
11/22/2023 +7 days 🔍
11/22/2023 +0 days 🔍
07/24/2024 +244 days 🔍

Sourcesinfo

Advisory: checkmk.com
Status: Confirmed

CVE: CVE-2023-6156 (🔍)
GCVE (CVE): GCVE-0-2023-6156
GCVE (VulDB): GCVE-100-245997

Entryinfo

Created: 11/22/2023 17:45
Updated: 07/24/2024 01:14
Changes: 11/22/2023 17:45 (47), 12/15/2023 20:17 (12), 07/24/2024 01:14 (15)
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!