Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Ignored storage errors on token revokation in ORY Fosite

CVSS 3.1 8.0 HIGHEUVD CVSS 3.1 8.0 CVSS 3.1 · [email protected] · Secondary 8.0 HIGHCVSS 3.1 · [email protected] · Primary 8.0 HIGHCVSS 2.0 · [email protected] · Primary 4.0 MEDIUMCVSS_V3 Publisher rating HIGHFixed by github.com/ory/fosite 0.34.0osv · severity unknownFixed by github.com/ory/fosite 0.34.0KEV status unknown

cve-program · CVE-2020-15223

Published

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

Read the publisher's advisory

euvd · EUVD-2021-1002

Published

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

Read the publisher's advisory

nvd · CVE-2020-15223

Published

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

Read the publisher's advisory

osv · GHSA-7mqr-2v3q-v2wm

Published

### Impact 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. ### References [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.

Read the publisher's advisory

osv · GO-2021-0109

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2020-15223

Published

fosite

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "product": "fosite",
                    "vendor": "ory",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "< 0.34.0"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2021-1002

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 24, 2020, 4:15:45 PM

dateUpdated: Aug 4, 2024, 1:08:22 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2020-15223

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-755 · CWE-754

Original publisher date fields

published: 2020-09-24T17:15:13.210

lastModified: 2026-06-17T02:56:18.113

1 source CPE criteria · context only
  • cpe:2.3:a:ory:fosite:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-7mqr-2v3q-v2wm

Published

github.com/ory/fosite

Go

SEMVER · introduced 0 → fixed 0.34.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2021-0109

Published

github.com/ory/fosite

Go

SEMVER · introduced 0 → fixed 0.34.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 05:53 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current