CVE-2018-10894: Medium severity redhat keycloak vulnerability

Published Jul 9, 2018
·
Updated

It was found that SAML authentication in Keycloak 3.4.3.Final incorrectly authenticated expired certificates. A malicious user could use this to access unauthorized data or possibly conduct further attacks.

Other sources

It was found that SAML authentication in Keycloak incorrectly authenticated expired certificates. A malicious user could use this to access unauthorized data or possibly conduct further attacks.

Red Hat

Affected Software

7 affected componentsFixes available
maven/org.keycloak:keycloak-services<4.4.0.Final
4.4.0.Final
maven/org.keycloak:keycloak-saml-adapter-core<4.4.0.Final
4.4.0.Final
redhat/keycloak<4.4.0.
4.4.0.
redhat keycloak=3.4.3
redhat Single Sign-on=7.2
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.keycloak:keycloak-services to a version that resolves this vulnerability.

    Fixed in 4.4.0.Final
  2. Upgrade

    Upgrade maven/org.keycloak:keycloak-saml-adapter-core to a version that resolves this vulnerability.

    Fixed in 4.4.0.Final
  3. Upgrade

    Upgrade redhat/keycloak to a version that resolves this vulnerability.

    Fixed in 4.4.0.

Event History

Jul 9, 2018
Data Sourced
via Red Hat·07:41 PM
DescriptionSeverityAffected Software
Aug 1, 2018
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
DescriptionSeverityWeakness
May 13, 2022
Advisory Published
01:34 AM

Frequently Asked Questions

1

What is the severity of CVE-2018-10894?

CVE-2018-10894 has a high severity rating due to its potential to allow unauthorized access through expired certificates.

2

How do I fix CVE-2018-10894?

To fix CVE-2018-10894, upgrade to Keycloak version 4.4.0.Final or later.

3

What systems are affected by CVE-2018-10894?

CVE-2018-10894 affects Keycloak versions prior to 4.4.0.Final.

4

Can CVE-2018-10894 lead to data breaches?

Yes, CVE-2018-10894 can allow a malicious user to access unauthorized data.

5

Is there a workaround for CVE-2018-10894?

There are no known workarounds for CVE-2018-10894; upgrading is the recommended solution.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203