Security Resilience

CVE-2023-6841

Redhat Keycloak

Published
10 September 2024
Modified
01 October 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0074 53th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-6841 is a high-severity Improper Handling of Extra Values (CWE-231) vulnerability in Redhat Keycloak. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A denial of service vulnerability was found in keycloak where the amount of attributes per object is not limited,an attacker by sending repeated HTTP requests could cause a resource exhaustion when the application send back rows with long attribute values.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-6927Same product: Redhat Keycloak
CVE-2023-0105Same product: Redhat Keycloak
CVE-2023-0091Same product: Redhat Keycloak
CVE-2023-4918Same product: Redhat Keycloak
CVE-2024-1722Same product: Redhat Keycloak
CVE-2025-8419Same product: Redhat Keycloak
CVE-2025-5416Same product: Redhat Keycloak
CVE-2024-7341Same product: Redhat Keycloak
CVE-2023-2422Same product: Redhat Keycloak
CVE-2025-7365Same product: Redhat Keycloak

Affected Assets

redhat
keycloak
all versions
redhat
single sign-on
7.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly enforces correct handling of the number and format of supplied values, stopping extra values from being accepted or processed.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices directly require robust input validation that prevents improper handling of extra values.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Secure development lifecycle includes input validation and parameter handling that can prevent extra-value processing flaws.

blocks

A.8.26 only requires that security requirements (including input validation and resilience against injections) be identified and specified during development or acquisition; it does not itself enforce, implement or assure those requirements in a way that stops extra values from being exploitable.

blocks

Secure architecture principles encourage robust input handling but do not specifically address extra-value scenarios.

prevents

Secure coding standards directly require validation of the exact number and type of input parameters.

finds

Security testing can detect extra-value handling issues but does not prevent them by itself.

References