First published: Fri May 03 2019(Updated: )
A flaw was found in Keycloak before version 11.0.0, where the code base contains usages of ObjectInputStream without type checks. This flaw allows an attacker to inject arbitrarily serialized Java Objects, which would then get deserialized in a privileged context and potentially lead to remote code execution.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.keycloak:keycloak-common | <11.0.0 | 11.0.0 |
maven/org.keycloak:keycloak-core | <11.0.0 | 11.0.0 |
Redhat Keycloak | <11.0.0 | |
Redhat Decision Manager | =7.0 | |
Redhat Jboss Fuse | =7.0.0 | |
Redhat Openshift Application Runtimes | ||
Redhat Process Automation | =7.0 | |
Redhat Single Sign-on | =7.0 | |
Quarkus Quarkus | <=1.4.2 |
There is currently no known mitigation for this issue.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2020-1714 is a vulnerability in Keycloak that allows an attacker to inject arbitrarily serialized Java Objects.
The severity of CVE-2020-1714 is high with a CVSS score of 8.8.
CVE-2020-1714 affects Keycloak before version 11.0.0 by allowing the code base to contain usages of ObjectInputStream without type checks.
An attacker can exploit CVE-2020-1714 by injecting arbitrarily serialized Java Objects, which will get deserialized in a privileged context and potentially lead to remote code execution.
To fix CVE-2020-1714, it is recommended to upgrade Keycloak to version 11.0.0 or higher.