VDB-234165 · CVE-2023-38200 · EUVD-2023-2332

keylime Registrar denial of service

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.
6.1	$0-$5k	0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in keylime. This affects an unknown function of the component Registrar Handler. Performing a manipulation results in denial of service. This vulnerability is known as CVE-2023-38200. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in keylime (affected version unknown). This affects an unknown functionality of the component Registrar Handler. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability.

The weakness was published 07/14/2023. The advisory is shared at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2023-38200 since 07/13/2023. 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.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-2332). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

keylime

Website

Product: https://github.com/keylime/keylime/

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.2
VulDB Meta Temp Score: 6.1

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

NVD Base Score: 7.5
NVD Vector: 🔍

CNA Base Score: 7.5
CNA Vector (Red Hat, Inc.): 🔍

CVSSv2info

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

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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 Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Patch: github.com

Timelineinfo

07/13/2023 🔍
07/14/2023 +1 days 🔍
07/14/2023 +0 days 🔍
08/31/2025 +779 days 🔍

Sourcesinfo

Product: github.com

Advisory: bugzilla.redhat.com
Status: Confirmed

CVE: CVE-2023-38200 (🔍)
GCVE (CVE): GCVE-0-2023-38200
GCVE (VulDB): GCVE-100-234165
EUVD: 🔍

Entryinfo

Created: 07/14/2023 08:22
Updated: 08/31/2025 09:47
Changes: 07/14/2023 08:22 (35), 08/05/2023 19:22 (2), 08/05/2023 19:30 (12), 09/16/2024 17:30 (28), 08/31/2025 09:47 (5)
Complete: 🔍
Cache ID: 216::103

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