What is the severity of CVE-2018-14637?

CVE-2018-14637 has been classified with a high severity due to its potential for replay attacks.

How do I fix CVE-2018-14637?

To resolve CVE-2018-14637, upgrade Keycloak to version 4.6.0.Final or later.

What specific systems are affected by CVE-2018-14637?

CVE-2018-14637 affects Keycloak versions prior to 4.6.0.Final.

What type of attack can CVE-2018-14637 facilitate?

CVE-2018-14637 can facilitate replay attacks due to the ignoring of expiration conditions on SAML assertions.

Is there a workaround for CVE-2018-14637?

There is no known workaround for CVE-2018-14637; upgrading to the patched version is the recommended approach.

Vulnerability/
CVE-2018-14637

high

8.1

CWE

287 285

11/9/2018

30/11/2018

5/8/2024

CVE-2018-14637

First published: Tue Sep 11 2018(Updated: )

The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
redhat/Keycloak	<4.6.0.	4.6.0.
Red Hat Keycloak	<4.6.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-14637?
CVE-2018-14637 has been classified with a high severity due to its potential for replay attacks.
How do I fix CVE-2018-14637?
To resolve CVE-2018-14637, upgrade Keycloak to version 4.6.0.Final or later.
What specific systems are affected by CVE-2018-14637?
CVE-2018-14637 affects Keycloak versions prior to 4.6.0.Final.
What type of attack can CVE-2018-14637 facilitate?
CVE-2018-14637 can facilitate replay attacks due to the ignoring of expiration conditions on SAML assertions.
Is there a workaround for CVE-2018-14637?
There is no known workaround for CVE-2018-14637; upgrading to the patched version is the recommended approach.

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

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-14637?
CVE-2018-14637 has been classified with a high severity due to its potential for replay attacks.
How do I fix CVE-2018-14637?
To resolve CVE-2018-14637, upgrade Keycloak to version 4.6.0.Final or later.
What specific systems are affected by CVE-2018-14637?
CVE-2018-14637 affects Keycloak versions prior to 4.6.0.Final.
What type of attack can CVE-2018-14637 facilitate?
CVE-2018-14637 can facilitate replay attacks due to the ignoring of expiration conditions on SAML assertions.
Is there a workaround for CVE-2018-14637?
There is no known workaround for CVE-2018-14637; upgrading to the patched version is the recommended approach.