CVE-2020-10770: vulnerability in keycloak
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
72Vexday Risk Score
Patch now. It exploitation observed in the wild and has a working public exploit.
ssvc Actepss 70%
from disclosure to weapon182 days
Published on NVDDec 15
1st PoC+182d
Observed exploitation+1133d
What the vendors declare (VEX)
Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.
Red HatVEX document ↗
Fixed
4 products (10 components)
Red Hat Single Sign-On 7.4 for RHEL 6 Server · Red Hat Single Sign-On 7.4 for RHEL 7 Server · Red Hat Single Sign-On 7.4 for RHEL 8 · Red Hat Single Sign-On 7.4.5
Not affected
5 products — because the vulnerable code is not present in the product
Red Hat Decision Manager 7 · Red Hat Fuse 7 · Red Hat OpenShift Application Runtimes · Red Hat Process Automation 7 · Red Hat support for Spring Boot
A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using the OIDC parameter request_uri. This flaw allows an attacker to use this parameter to execute a Server-side request forgery (SSRF) attack.
Affected products
n/a · keycloakpublic PoCs found — 4
exploitdbwww.exploit-db.com/exploits/50405unverifiedgithubgithub.com/ColdFusionX/Keycloak-12.0.1-CVE-2020-10770★ 9githubgithub.com/0xlyvio/CVE-2020-10770-keycloak-exploit-poc★ 2cve_referencepacketstormsecurity.com/files/164499/Keycloak-12.0.1-Server-Side-Request-Forgery.htmlunverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.