CVE-2020-35509: Input Validation

Published Jan 4, 2021
·
Updated

A flaw was found in keycloak affecting versions 11.0.3 and 12.0.0. An expired certificate would be accepted by the direct-grant authenticator because of missing time stamp validations. The highest threat from this vulnerability is to data confidentiality and integrity.

Other sources

A flaw was found in keycloak. An expired certificate would be accepted by the direct-grant authenticator because of missing time stamp validations. The highest threat from this vulnerability is to data confidentiality and integrity.

Depending on the webserver configuration, a malicious user can supply an expired certificate and it would be accepted by Keycloak direct-grant authenticator. This is because Keycloak does not trigger the appropriate timestamp validation.

X509 Direct Grant: https://github.com/keycloak/keycloak/blob/4f330f4a57cbfcf6202b60546518261c66e59a35/services/src/main/java/org/keycloak/authentication/authenticators/x509/ValidateX509CertificateUsername.java#L74-L76

It would seem like PR https://github.com/keycloak/keycloak/pull/6330 missed a spot in adding the validateTimestamps call.

https://issues.redhat.com/browse/KEYCLOAK-16450

Red Hat

keycloak accepts an expired certificate by the direct-grant authenticator because of missing time stamp validations. The highest threat from this vulnerability is to data confidentiality and integrity.

This issue was partially fixed in version 13.0.1 and more completely fixed in version 14.0.0.

GitHub

Affected Software

6 affected componentsFixes available
redhat/rh-sso7-keycloak<0:9.0.15-1.redhat_00002.1.el6
0:9.0.15-1.redhat_00002.1.el6
redhat/rh-sso7-keycloak<0:9.0.15-1.redhat_00002.1.el7
0:9.0.15-1.redhat_00002.1.el7
redhat/rh-sso7-keycloak<0:9.0.15-1.redhat_00002.1.el8
0:9.0.15-1.redhat_00002.1.el8
redhat keycloak=11.0.3
redhat keycloak=12.0.0
maven/org.keycloak:keycloak-core<14.0.0
14.0.0

Event History

Jan 4, 2021
CVE Published
12:00 AM
Data Sourced
via Red Hat·12:40 PM
DescriptionSeverityAffected Software
Aug 23, 2022
CVE Published
via MITRE·03:53 PM
Data Sourced
via MITRE·03:53 PM
DescriptionWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Aug 24, 2022
Advisory Published
via GitHub·12:00 AM
Data Sourced
via GitHub·12:00 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the vulnerability ID for this flaw in Keycloak?

The vulnerability ID for this flaw in Keycloak is CVE-2020-35509.

2

What is the severity of CVE-2020-35509?

The severity of CVE-2020-35509 is medium.

3

Which versions of Keycloak are affected by CVE-2020-35509?

Versions 11.0.3 and 12.0.0 of Keycloak are affected by CVE-2020-35509.

4

What is the highest threat from CVE-2020-35509?

The highest threat from CVE-2020-35509 is to data confidentiality and integrity.

5

How can I fix the vulnerability CVE-2020-35509 in Keycloak?

To fix the vulnerability CVE-2020-35509 in Keycloak, update to version 9.0.15-1.redhat_00002.1.el6, 9.0.15-1.redhat_00002.1.el7, or 9.0.15-1.redhat_00002.1.el8.

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