What is the severity of CVE-2018-10912?

CVE-2018-10912 is rated as a high severity vulnerability due to its potential to cause Denial of Service in Keycloak environments.

How do I fix CVE-2018-10912?

To mitigate CVE-2018-10912, upgrade Keycloak to version 4.0.0 or later.

Who is affected by CVE-2018-10912?

CVE-2018-10912 affects users of Keycloak versions prior to 4.0.0, particularly in clustered environments.

What are the consequences of CVE-2018-10912?

Exploiting CVE-2018-10912 can lead to an infinite loop situation causing Denial of Service for Keycloak instances.

Is a patch available for CVE-2018-10912?

Yes, a patch is available through the official upgrade to Keycloak version 4.0.0 and above.

Vulnerability/
CVE-2018-10912

medium

4.9

CWE

835

23/7/2018

5/8/2024

CVE-2018-10912

First published: Mon Jul 23 2018(Updated: )

keycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement. A Keycloak cluster with multiple nodes could mishandle an expired session replacement and lead to an infinite loop. A malicious authenticated user could use this flaw to achieve Denial of Service on the server.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
redhat/Keycloak	<4.0.0.	4.0.0.
Red Hat Keycloak	<4.0.0
redhat single sign-on	=7.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-10912?
CVE-2018-10912 is rated as a high severity vulnerability due to its potential to cause Denial of Service in Keycloak environments.
How do I fix CVE-2018-10912?
To mitigate CVE-2018-10912, upgrade Keycloak to version 4.0.0 or later.
Who is affected by CVE-2018-10912?
CVE-2018-10912 affects users of Keycloak versions prior to 4.0.0, particularly in clustered environments.
What are the consequences of CVE-2018-10912?
Exploiting CVE-2018-10912 can lead to an infinite loop situation causing Denial of Service for Keycloak instances.
Is a patch available for CVE-2018-10912?
Yes, a patch is available through the official upgrade to Keycloak version 4.0.0 and above.

agent/type
agent/first-publish-date
agent/weakness
agent/references
agent/author
agent/description
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2018-10912
agent/software-canonical-lookup
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/event
agent/softwarecombine
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
package-manager/redhat
vendor/redhat
canonical/red hat keycloak
canonical/redhat single sign-on
version/redhat single sign-on/7.2

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-10912?
CVE-2018-10912 is rated as a high severity vulnerability due to its potential to cause Denial of Service in Keycloak environments.
How do I fix CVE-2018-10912?
To mitigate CVE-2018-10912, upgrade Keycloak to version 4.0.0 or later.
Who is affected by CVE-2018-10912?
CVE-2018-10912 affects users of Keycloak versions prior to 4.0.0, particularly in clustered environments.
What are the consequences of CVE-2018-10912?
Exploiting CVE-2018-10912 can lead to an infinite loop situation causing Denial of Service for Keycloak instances.
Is a patch available for CVE-2018-10912?
Yes, a patch is available through the official upgrade to Keycloak version 4.0.0 and above.