Keycloak Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

2.05
2.15
2.25
2.35
7.x5

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix59
Temporary Fix0
Workaround0
Unavailable0
Not Defined50

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional1
Proof-of-Concept2
Unproven0
Not Defined106

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical1
Local4
Adjacent30
Network74

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High7
Low62
None40

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required33
None76

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤30
≤417
≤521
≤632
≤725
≤810
≤94
≤100

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤31
≤418
≤520
≤633
≤727
≤86
≤94
≤100

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤35
≤425
≤528
≤628
≤711
≤810
≤92
≤100

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤31
≤42
≤511
≤613
≤718
≤813
≤910
≤107

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤42
≤58
≤62
≤75
≤84
≤92
≤104

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k23
<2k72
<5k8
<10k3
<25k3
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k103
<2k5
<5k0
<10k1
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (62): 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 1, 1.0.1, 1.0.2, 1.0.3, 2, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, 3.2.1.Final, 3.4, 3.4.1, 3.4.3.Final, 4.0, 4.0.0.Beta2, 4.2.1.Final, 4.3.0.Final, 4.8, 4.8.1, 4.8.2, 6, 6.0, 6.0.1, 6.0.2, 7.0, 7.0.1, 8, 8.0, 8.0.1, 8.0.2, 9, 9.0, 9.0.1, 10.0, 10.0.1, 11.0, 11.0.3, 12, 12.0, 12.0.1, 13.0, 15.0, 15.1, 20.0, 20.0.1, 20.0.2, 22.0.5

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
04/17/20245.75.7Keycloak redirect_uri$0-$5k$0-$5kNot DefinedNot Defined0.24CVE-2024-2419
04/16/20243.53.5Keycloak SAML cross site scripting$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2023-6717
04/16/20243.53.5Keycloak checkLoginIframe cross-domain policy$0-$5k$0-$5kNot DefinedNot Defined0.29CVE-2024-1249
04/16/20243.53.5Keycloak URL redirect$0-$5k$0-$5kNot DefinedNot Defined0.34CVE-2024-1132
04/16/20243.53.5Keycloak Client Registration authorization$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2023-6544
04/16/20245.55.5Keycloak Token Type Privilege Escalation$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2023-0657
04/16/20246.36.3Keycloak Client Step-Up Authentication improper authentication$0-$5k$0-$5kNot DefinedNot Defined0.15CVE-2023-3597
02/21/20243.63.4Keycloak Account Lockout denial of service$0-$5k$0-$5kProof-of-ConceptNot Defined0.00CVE-2024-1722
02/21/20245.55.5Keycloak improper authentication$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2023-6787
12/18/20234.74.7Red Hat Keycloak JARM Response redirect$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2023-6927
12/15/20234.34.1JBoss KeyCloak lowerCaseHostname redirect$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2023-6291
12/15/20237.16.9Red Hat keycloak/Single Sign-On/Middleware Container/ Admin User Interface allocation of resources$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2023-6563
12/12/20234.54.5JBoss KeyCloak Incomplete Fix CVE-2020-10748 cross site scripting$0-$5k$0-$5kNot DefinedNot Defined0.02CVE-2023-6134
12/04/20234.34.3JBoss KeyCloak WebAuthn injection$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2023-6484
11/30/20235.55.3Keycloak Login ldap injection$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-2232
09/13/20236.56.5Keycloak User Registration cleartext transmission$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2023-4918
06/28/20236.56.5Keycloak URL Scheme cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-4361
06/27/20235.55.5Keycloak Device improper authorization$0-$5k$0-$5kNot DefinedNot Defined0.02CVE-2023-2585
06/27/20234.64.6Keycloak mTLS Authentication certificate validation$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2023-2422
05/23/20235.75.7keycloak certificate validation$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2023-1664
04/28/20237.77.6HYPR Keycloak Authenticator Extension improper authentication$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-1477
03/03/20234.94.7keycloak-connect Node.js Adapter redirect$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2022-2237
03/03/20235.55.3Keycloak data authenticity$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2023-0264
03/01/20233.53.4Keycloak OpenID Connect Login Service cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-4137
03/01/20233.53.3Keycloak cross site scripting$0-$5k$0-$5kProof-of-ConceptNot Defined0.04CVE-2022-1438

84 more entries are not shown

Do you want to use VulDB in your project?

Use the official API to access entries easily!