CVE-2023-6841
Redhat Keycloak
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS 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
- 🇪🇺 ENISA EUVD: EUVD-2024-2886
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
CVEs Like This One
Affected Assets
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.
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.
Secure development lifecycle includes input validation and parameter handling that can prevent extra-value processing flaws.
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.
Secure architecture principles encourage robust input handling but do not specifically address extra-value scenarios.
Secure coding standards directly require validation of the exact number and type of input parameters.
Security testing can detect extra-value handling issues but does not prevent them by itself.