KeycloakApplication · Redhat
CVE-2023-6841
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA denial of service vulnerability in Keycloak allows attackers to exhaust server resources by sending repeated HTTP requests that trigger responses containing objects with unlimited attributes and long attribute values, leading to resource exhaustion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
KeycloakApplication
all versions
Single Sign OnApplication
= 7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Keycloak or RH SSO is runningCheck the running services/processes, or review application dependencies and configurations for Keycloak or Red Hat Single Sign-On instancesAffected if The system is running any version of Keycloak or RH SSO 7.0 without attribute limit configuration
-
Check for attribute count limits in Keycloak configurationReview Keycloak configuration files (standalone.xml, standalone-ha.xml, or keycloak.conf) for any settings related to attribute limits, max attributes, or similar resource limitsAffected if No attribute count limits are configured in Keycloak settings
-
Check for attribute value length limitsReview Keycloak configuration for settings controlling maximum attribute value length or string length limitsAffected if No maximum attribute value length is configured or enforced
-
Check for request rate limiting or throttlingReview any reverse proxy, load balancer, or Keycloak-level rate limiting configurations that may limit repeated requests from the same sourceAffected if No rate limiting or request throttling is in place to mitigate repeated requests
-
Monitor for resource exhaustion symptomsCheck server logs, CPU/memory usage, and connection pool status for signs of resource exhaustion that could indicate exploitationAffected if Logs show unusual resource consumption patterns or connection issues consistent with the described attack vector
A system is affected if it runs any version of Keycloak or RH SSO 7.0 without configured limits on the number of attributes per object and the maximum length of attribute values.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement limits on the number of attributes per object and the maximum length of attribute values in Keycloak's configuration or code to prevent resource exhaustion from repeated requests.
Fix this in Keycloak
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6841 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-6841 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data