Skip to content

GHSA-4fgq-gq9g-3rw7 CVE-2019-10201

Improper Verification of Cryptographic Signature in keycloak

High Maven
Severity
8.1 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.71%
Chance of exploitation in the next 30 days. Higher than 53.71% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-347 Improper Verification of Cryptographic Signature
Fix
7.0.0
Upgrade org.keycloak:keycloak-core to this version or later

Description

It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information.

Affected versions

Maven

PackageVulnerableFixed in
org.keycloak:keycloak-core
< 7.0.0
7.0.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.keycloak:keycloak-core Maven → 7.0.0

maven
<dependency><groupId>org.keycloak</groupId><artifactId>keycloak-core</artifactId><version>7.0.0</version></dependency>
gradle
implementation("org.keycloak:keycloak-core:7.0.0")

Severity breakdown

CVSS 3.1 8.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Weakness

CWE-347: Improper Verification of Cryptographic Signature

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-q4xq-445g-g6ch
Keycloak allows cross-site scripting (XSS)
Low Also affects org.keycloak:keycloak-core
GHSA-93ww-43rr-79v3
Keycloak mTLS Authentication Bypass via Reverse Proxy TLS Termination
High Also affects org.keycloak:keycloak-core
GHSA-w97f-w3hq-36g2
Keycloak Denial of Service vulnerability
High Also affects org.keycloak:keycloak-core
GHSA-xmmm-jw76-q7vg
Keycloaks's One Time Passcode (OTP) is valid longer than expiration timeSeverity
Medium Also affects org.keycloak:keycloak-core
GHSA-g4gc-rh26-m3p5
Keycloak Open Redirect vulnerability
Medium Also affects org.keycloak:keycloak-core
GHSA-9vm7-v8wj-3fqw
keycloak-core: open redirect via "form_post.jwt" JARM response mode
Medium Also affects org.keycloak:keycloak-core
GHSA-5q66-v53q-pm35
Keycloak vulnerable to Plaintext Storage of User Password
High Also affects org.keycloak:keycloak-core
GHSA-5cc8-pgp5-7mpm
Keycloak Untrusted Certificate Validation vulnerability
Medium Also affects org.keycloak:keycloak-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor