VDB-260949 · CVE-2023-6544 · RHSA-2024:1860

Keycloak Client Registration authorization

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

Summaryinfo

A vulnerability has been found in Keycloak and classified as problematic. The impacted element is an unknown function of the component Client Registration Handler. Performing a manipulation results in authorization. This vulnerability is cataloged as CVE-2023-6544. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Keycloak (the affected version unknown). This affects an unknown part of the component Client Registration Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on integrity.

The advisory is shared at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2023-6544 since 12/06/2023. The exploitability is told to be easy. 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-2024-1087). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Keycloak

License

open-source

CPE 2.3info

🔍

CPE 2.2info

🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

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

CNA Base Score: 5.4
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: Authorization
CWE: CWE-639 / CWE-285 / CWE-266
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: 🔍

Timelineinfo

12/06/2023 🔍
04/16/2024 +131 days 🔍
04/16/2024 +0 days 🔍
11/11/2025 +574 days 🔍

Sourcesinfo

Advisory: RHSA-2024:1860
Status: Not defined

CVE: CVE-2023-6544 (🔍)
GCVE (CVE): GCVE-0-2023-6544
GCVE (VulDB): GCVE-100-260949
EUVD: 🔍

Entryinfo

Created: 04/16/2024 20:02
Updated: 11/11/2025 17:23
Changes: 04/16/2024 20:02 (48), 05/23/2024 13:44 (2), 05/23/2024 13:49 (12), 11/11/2025 17:23 (2)
Complete: 🔍
Cache ID: 216::103

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