CVE-2020-10770: 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
Noroxi assessment
Priority: Plan (action score 42/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 69.7% (FIRST EPSS); higher than 99.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.keycloak:keycloak-core (Maven) 13.0.0; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.11-1.redhat_00001.1.el6sso; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.11-1.redhat_00001.1.el6sso.
Add it to your regular patch cycle. Upgrade to org.keycloak:keycloak-core (Maven) 13.0.0; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.11-1.redhat_00001.1.el6sso; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.11-1.redhat_00001.1.el6sso or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 15, 2020
- Updated
- Jun 16, 2026
- EPSS
- 69.7% · 99th percentile
- CWE
- CWE-918
Report tools
Action score
42
Plan
Add it to your regular patch cycle.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 21 / 30 · 69.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | keycloak | cpe:2.3:a:redhat:keycloak |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat keycloakbefore 12.0.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a keycloak
- keycloak 13.0.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.keycloak:keycloak-core | before 13.0.0 | 13.0.0 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak | before 0:9.0.11-1.redhat_00001.1.el6sso | 0:9.0.11-1.redhat_00001.1.el6sso |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak-server | before 0:9.0.11-1.redhat_00001.1.el6sso | 0:9.0.11-1.redhat_00001.1.el6sso |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak | before 0:9.0.11-1.redhat_00001.1.el7sso | 0:9.0.11-1.redhat_00001.1.el7sso |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak-server | before 0:9.0.11-1.redhat_00001.1.el7sso | 0:9.0.11-1.redhat_00001.1.el7sso |
| Red Hat:red_hat_single_sign_on:7::el8 | rh-sso7-keycloak | before 0:9.0.11-1.redhat_00001.1.el8sso | 0:9.0.11-1.redhat_00001.1.el8sso |
| Red Hat:red_hat_single_sign_on:7::el8 | rh-sso7-keycloak-server | before 0:9.0.11-1.redhat_00001.1.el8sso | 0:9.0.11-1.redhat_00001.1.el8sso |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-1245A privilege escalation flaw was found in the token exchange feature of keycloak.39Monitor
- CVE-2019-14910A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS fro39Monitor
- CVE-2022-3782keycloak: path traversal via double URL encoding.38Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-10776Nov 16, 2020 · A flaw was found in Keycloak before version 12.0.0, where it is possible to add unsafe schemes for the redirect_uri parameter.19Monitor
- ← EarlierCVE-2020-14389Nov 16, 2020 · It was found that Keycloak before version 12.0.0 would permit a user with only view-profile role to manage the resources in the new account 32Monitor
- Later →CVE-2020-14302Dec 15, 2020 · A flaw was found in Keycloak before 13.0.0 where an external identity provider, after successful authentication, redirects to a Keycloak end19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.keycloak:keycloak-core | 13.0.0 | Package registry (OSV) |
| red hat:rh-sso7-keycloak | 0:9.0.11-1.redhat_00001.1.el6sso · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-keycloak-server | 0:9.0.11-1.redhat_00001.1.el6sso · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2021-10-13 |
| Nuclei detection template | Nuclei template CVE-2020-10770 | — |
| Proof-of-concept repository on GitHub | stars:9 | 2021-10-13 |
| Proof-of-concept repository on GitHub | stars:2 | 2026-09-05 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+301 d
- TodayOct 30, 2026+2145 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.