Skip to content
Noroxi
CVE-2024-7341· NVD / CVE Program· CNA redhat

Wildfly-elytron: org.keycloak/keycloak-services: session fixation in elytron saml adapters

A session fixation issue was discovered in the SAML adapters provided by Keycloak. The session ID and JSESSIONID cookie are not changed at login time, even when the turnOffChangeSessionIdOnLogin option is configured. This flaw allows an attacker who hijacks the current session before authentication to trigger session fixation.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Sep 9, 2024
Updated
Aug 27, 2026
EPSS
0.8% · 56th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.1
CNA · redhat
7.1
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
redhatkeycloak
redhatsingle sign-on
redhatenterprise linux
redhatbuild of keycloak

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • redhat build of keycloak22.0 and later · before 22.0.12
  • redhat build of keycloak24.0 and later · before 24.0.7
  • redhat keycloakup to 25.0.2 inclusive
  • redhat single sign-on7.6 and later · before 7.6.10
  • redhat single sign-onall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • github.com/keycloak/keycloak org.keycloak:keycloak-services

    • before 22.0.12affected · semver
    • 23.0.0 and later · before 24.0.7affected · semver
    • 25.0.0 and later · before 25.0.5affected · semver
  • Red Hat Red Hat Build of Keycloak

    • all versionsunknown
    • all versionsunknown
  • Red Hat Red Hat build of Keycloak 22

    • 22.0.12-1 and laternot affected · rpm
    • 22-17 and laternot affected · rpm
    • 22-20 and laternot affected · rpm
  • Red Hat Red Hat build of Keycloak 24

    • 24.0.7-4 and laternot affected · rpm
    • 24-16 and laternot affected · rpm
    • 24-16 and laternot affected · rpm
  • Red Hat Red Hat JBoss Enterprise Application Platform 8

    • all versionsunknown
  • Red Hat Red Hat Single Sign-On 7

    • all versionsunknown
  • Red Hat Red Hat Single Sign-On 7.6 for RHEL 7

    • 0:18.0.16-1.redhat_00001.1.el7sso and laternot affected · rpm
  • Red Hat Red Hat Single Sign-On 7.6 for RHEL 8

    • 0:18.0.16-1.redhat_00001.1.el8sso and laternot affected · rpm
  • Red Hat Red Hat Single Sign-On 7.6 for RHEL 9

    • 0:18.0.16-1.redhat_00001.1.el9sso and laternot affected · rpm
  • Red Hat RHEL-8 based Middleware Containers

    • 7.6-52 and laternot affected · rpm

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.keycloak:keycloak-servicesfrom 23.0.0 · before 24.0.724.0.7
Mavenorg.keycloak:keycloak-servicesfrom 25.0.0 · before 25.0.525.0.5
Mavenorg.keycloak:keycloak-servicesbefore 22.0.1222.0.12
Red Hat:red_hat_single_sign_on:7.6::el7rh-sso7-keycloakbefore 0:18.0.16-1.redhat_00001.1.el7sso0:18.0.16-1.redhat_00001.1.el7sso
Red Hat:red_hat_single_sign_on:7.6::el7rh-sso7-keycloak-serverbefore 0:18.0.16-1.redhat_00001.1.el7sso0:18.0.16-1.redhat_00001.1.el7sso
Red Hat:red_hat_single_sign_on:7.6::el8rh-sso7-keycloakbefore 0:18.0.16-1.redhat_00001.1.el8sso0:18.0.16-1.redhat_00001.1.el8sso
Red Hat:red_hat_single_sign_on:7.6::el8rh-sso7-keycloak-serverbefore 0:18.0.16-1.redhat_00001.1.el8sso0:18.0.16-1.redhat_00001.1.el8sso
Red Hat:red_hat_single_sign_on:7.6::el9rh-sso7-keycloakbefore 0:18.0.16-1.redhat_00001.1.el9sso0:18.0.16-1.redhat_00001.1.el9sso
Red Hat:red_hat_single_sign_on:7.6::el9rh-sso7-keycloak-serverbefore 0:18.0.16-1.redhat_00001.1.el9sso0:18.0.16-1.redhat_00001.1.el9sso

Other highest-scoring records for the same primary product.

  • CVE-2020-10770A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using the OIDC parameter
    42Plan
  • CVE-2022-1245A privilege escalation flaw was found in the token exchange feature of keycloak.
    39Monitor
  • CVE-2019-14910A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS fro
    39Monitor
  • CVE-2022-3782keycloak: path traversal via double URL encoding.
    38Monitor
  • CVE-2021-20195A flaw was found in keycloak in versions before 13.0.0.
    38Monitor
  • CVE-2019-14837A flaw was found in keycloack before version 8.0.0.
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
github.com/keycloak/keycloak org.keycloak:keycloak-services22.0.12Vendor (CNA)
github.com/keycloak/keycloak org.keycloak:keycloak-services24.0.7Vendor (CNA)
github.com/keycloak/keycloak org.keycloak:keycloak-services25.0.5Vendor (CNA)
Maven:org.keycloak:keycloak-services22.0.12Package registry (OSV)
Maven:org.keycloak:keycloak-services24.0.7Package registry (OSV)
Maven:org.keycloak:keycloak-services25.0.5Package registry (OSV)
red hat:rh-sso7-keycloak0:18.0.16-1.redhat_00001.1.el7sso · Red Hat:red_hat_single_sign_on:7.6::el7Package registry (OSV)
red hat:rh-sso7-keycloak-server0:18.0.16-1.redhat_00001.1.el7sso · Red Hat:red_hat_single_sign_on:7.6::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2022-3916355 days apartKeycloak: session takeover with oidc offline refreshtokens
    27Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-384 · Session Fixation

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records