{"id":"CVE-2020-15223","aliases":["EUVD-2021-1002","GHSA-7mqr-2v3q-v2wm","GO-2021-0109"],"status":"published","title":"Ignored storage errors on token revokation in ORY Fosite","description":"In ORY Fosite (the security first OAuth2 \u0026 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","severity":{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.01588,"percentile":0.75833,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-754","CWE-755"],"published":"2020-09-24T16:15:45Z","modified":"2026-10-20T10:51:53Z","fixes":[{"ecosystem":"Go","package":"github.com/ory/fosite","fixed_in":["0.34.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/ory/fosite","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.34.0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/ory/fosite","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.34.0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/ory/fosite","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.34.0"}]}]}],"products":[{"vendor":"ory","product":"fosite"}],"references":[{"url":"https://github.com/ory/fosite/security/advisories/GHSA-7mqr-2v3q-v2wm","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"https://tools.ietf.org/html/rfc7009#section-2.2.1","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15223","tags":["advisory"]},{"url":"https://pkg.go.dev/vuln/GO-2021-0109","tags":["web"]},{"url":"https://github.com/advisories/GHSA-7mqr-2v3q-v2wm"}],"sources":{"cve":[{"id":"CVE-2020-15223","title":"Ignored storage errors on token revokation in ORY Fosite","description":"In ORY Fosite (the security first OAuth2 \u0026 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","status":"published","published":"2020-09-24T16:15:45Z","modified":"2024-08-04T13:08:22.904Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high","assessor":"cna"}],"cwes":["CWE-755"],"updated_at":"2026-11-02T14:35:50.228781Z"}],"euvd":[{"id":"EUVD-2021-1002","description":"In ORY Fosite (the security first OAuth2 \u0026 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","status":"published","published":"2020-09-24T16:15:45Z","modified":"2024-08-04T13:08:22Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-03T03:07:32.55679Z"}],"ghsa":[{"id":"GHSA-7mqr-2v3q-v2wm","title":"Ory fosite contains Improper Handling of Exceptional Conditions ","description":"### Impact\nThe `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.\n\n### References\n[RFC 7009](https://tools.ietf.org/html/rfc7009#section-2.2.1) states that a 503 HTTP code must be returned when the server has a problem.","status":"published","published":"2021-05-24T16:57:39Z","modified":"2023-02-14T00:21:05Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-754","CWE-755"],"updated_at":"2026-11-02T14:36:44.81167Z"}],"nvd":[{"id":"CVE-2020-15223","description":"In ORY Fosite (the security first OAuth2 \u0026 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","status":"published","published":"2020-09-24T17:15:13.21Z","modified":"2026-06-17T02:56:18.113Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high","assessor":"secondary"},{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high","assessor":"primary"},{"version":"2.0","score":4,"vector":"AV:N/AC:H/Au:N/C:P/I:P/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-755","CWE-754"],"updated_at":"2026-11-02T14:06:15.83396Z"}],"osv":[{"id":"CVE-2020-15223","description":"In ORY Fosite (the security first OAuth2 \u0026 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","status":"published","published":"2020-09-24T17:15:13.21Z","modified":"2026-10-20T10:51:53.321910063Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:44:14.828228Z"},{"id":"GHSA-7mqr-2v3q-v2wm","title":"Ory fosite contains Improper Handling of Exceptional Conditions ","description":"### Impact\nThe `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.\n\n### References\n[RFC 7009](https://tools.ietf.org/html/rfc7009#section-2.2.1) states that a 503 HTTP code must be returned when the server has a problem.","status":"published","published":"2021-05-24T16:57:39Z","modified":"2026-09-10T03:49:04.760073152Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-754","CWE-755"],"updated_at":"2026-11-02T15:46:41.349637Z"},{"id":"GO-2021-0109","title":"Improper handling of token revocation in github.com/ory/fosite","description":"Due to improper error handling, an error with the underlying token storage may cause a user to believe a token has been successfully revoked when it is in fact still valid. An attackers ability to exploit this relies on an ability to trigger errors in the underlying storage.","status":"published","published":"2021-07-28T18:08:05Z","modified":"2024-05-20T16:03:47Z","updated_at":"2026-11-02T15:47:00.604718Z"}]}}