CVE-2020-10758: A vulnerability was found in Keycloak before 11.0.1 where DoS attack is possible by sending twenty requests simultaneously to the specified
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.9% (FIRST EPSS); higher than 80.2% 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-parent (Maven) 11.0.1; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.5-1.redhat_00001.1.el6sso; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.5-1.redhat_00001.1.el6sso.
Low priority for now. Upgrade to org.keycloak:keycloak-parent (Maven) 11.0.1; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.5-1.redhat_00001.1.el6sso; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.5-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 vulnerability was found in Keycloak before 11.0.1 where DoS attack is possible by sending twenty requests simultaneously to the specified keycloak server, all with a Content-Length header value that exceeds the actual byte count of the request body.
- Published
- Sep 16, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.9% · 80th percentile
- CWE
- CWE-770
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- 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 |
| redhat | openshift application runtimes | cpe:2.3:a:redhat:openshift_application_runtimes |
| redhat | single sign-on | cpe:2.3:a:redhat:single_sign-on |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat keycloakbefore 11.0.1
- redhat openshift application runtimesall versions
- redhat openshift application runtimes1.0
- redhat single sign-onall versions
- redhat single sign-on7.0
- redhat single sign-on7.4
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 before 11.0.1affected
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-parent | before 11.0.1 | 11.0.1 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak | before 0:9.0.5-1.redhat_00001.1.el6sso | 0:9.0.5-1.redhat_00001.1.el6sso |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak-server | before 0:9.0.5-1.redhat_00001.1.el6sso | 0:9.0.5-1.redhat_00001.1.el6sso |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak | before 0:9.0.5-1.redhat_00001.1.el7sso | 0:9.0.5-1.redhat_00001.1.el7sso |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak-server | before 0:9.0.5-1.redhat_00001.1.el7sso | 0:9.0.5-1.redhat_00001.1.el7sso |
| Red Hat:red_hat_single_sign_on:7::el8 | rh-sso7-keycloak | before 0:9.0.5-1.redhat_00001.1.el8sso | 0:9.0.5-1.redhat_00001.1.el8sso |
| Red Hat:red_hat_single_sign_on:7::el8 | rh-sso7-keycloak-server | before 0:9.0.5-1.redhat_00001.1.el8sso | 0:9.0.5-1.redhat_00001.1.el8sso |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-10770A 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 42Plan
- 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
Published before and after this one in the same product
- ← EarlierCVE-2020-1758May 15, 2020 · A flaw was found in Keycloak in versions before 10.0.0, where it does not perform the TLS hostname verification while sending emails using t23Monitor
- ← EarlierCVE-2020-1727Jun 22, 2020 · A vulnerability was found in Keycloak before 9.0.2, where every Authorization URL that points to an IDP server lacks proper input validation21Monitor
- Later →CVE-2020-10748Sep 16, 2020 · A flaw was found in Keycloak's data filter, in version 10.0.1, where it allowed the processing of data URLs in some circumstances.24Monitor
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-parent | 11.0.1 | Package registry (OSV) |
| red hat:rh-sso7-keycloak | 0:9.0.5-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.5-1.redhat_00001.1.el6sso · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
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.
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
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.