CVE-2023-6717 — keycloak-services
MEDIUMCVE-2023-6717 is a medium-severity (CVSS 6) Cross-site Scripting (XSS) vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.
Keycloak: xss via assertion consumer service url in saml post-binding flow
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-6717.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.keycloak:keycloak-services☕org.keycloak:keycloak-servicesReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A flaw was found in the SAML client registration in Keycloak that could allow an administrator to register malicious JavaScript URIs as Assertion Consumer Service POST Binding URLs (ACS), posing a Cross-Site Scripting (XSS) risk. This issue may allow a malicious admin in one realm or a client with registration access to target users in different realms or applications, executing arbitrary JavaScript in their contexts upon form submission. This can enable unauthorized access and harmful actions, compromising the confidentiality, integrity, and availability of the complete KC instance.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-services | all versions | 22.0.10org.keycloak:keycloak-services:22.0.10 |
| ☕Maven | org.keycloak:keycloak-services | ≥ 23.0.0&&< 24.0.3 | 24.0.3org.keycloak:keycloak-services:24.0.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-services, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-services to 22.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6717 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat AMQ Broker 7 | keycloak | RHSA-2024:2945 |
| Red Hat build of Keycloak 22 | rhbk/keycloak-operator-bundle:22.0.10-1 | RHSA-2024:1867 |
| Red Hat build of Keycloak 22.0.10 | keycloak | RHSA-2024:1868 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-data-index-ephemeral-rhel8:1.33.0-5 | RHSA-2024:4057 |
| RHPAM 7.13.5 async | see advisory | RHSA-2024:1353 |
Frequently Asked Questions
Is CVE-2023-6717 in your dependencies?
Find it across Maven, including transitive dependencies.