CVE-2023-6927
Keycloak: open redirect via "form_post.jwt" jarm response mode
No known exploitation. EPSS puts it in the 64th percentile. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
What it is
From the CVE record
A flaw was found in Keycloak. This issue may allow an attacker to steal authorization codes or tokens from clients using a wildcard in the JARM response mode "form_post.jwt" which could be used to bypass the security patch implemented to address CVE-2023-6134.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
1.1% chance of exploitation activity in the next 30 days, which ranks it in the 64th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
10 events over 1009 days, from the signal feeds we watch.
- Patch availableworkaround available, record updated
- OpenVAS check added
- Patch availableworkaround available, record updated
- Publishedweakness classified, att&ck mapped
Affected products
- keycloakOperating Systems / linux-distro
- single sign-onOperating Systems / linux-distro
- Red Hat build of Keycloak 22Security Products / identity-access-mgmt
- Red Hat build of Keycloak 22.0.8Security Products / identity-access-mgmt
- Red Hat Single Sign-On 7Security Products / identity-access-mgmt
- Red Hat Single Sign-On 7.6 for RHEL 7Security Products / identity-access-mgmt
- Red Hat Single Sign-On 7.6 for RHEL 8Security Products / identity-access-mgmt
- Red Hat Single Sign-On 7.6 for RHEL 9Security Products / identity-access-mgmt
And 2 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Scored 4.6 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required LowRequires basic user-level privileges
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity LowData modification is possible but limited in scope or consequence
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Initial AccessT1566Phishingmedium confidence
Sources
References in the record
- access.redhat.com/errata/RHSA-2024:0094
- access.redhat.com/errata/RHSA-2024:0095
- access.redhat.com/errata/RHSA-2024:0096
And 14 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Keycloak, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI