CVSS: 6.1EPSS: 0%CPEs: 1EXPL: 0CVE-2020-15233 – OAuth2 Redirect URL validity does not respect query parameters and character casing for loopback addresses
https://notcve.org/view.php?id=CVE-2020-15233
ORY Fosite is a security first OAuth2 & OpenID Connect framework for Go. In Fosite from version 0.30.2 and before version 0.34.1, there is an issue in which an an attacker can override the registered redirect URL by performing an OAuth flow and requesting a redirect URL that is to the loopback adapter. Attackers can provide both custom URL query parameters to their loopback redirect URL, as well as actually overriding the host of the registered redirect URL. These attacks are only applicable in scenarios where the attacker has access over the loopback interface. This vulnerability has been patched in ORY Fosite v0.34.1. • https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf https://github.com/ory/fosite/security/advisories/GHSA-rfq3-w54c-f9q5 • CWE-20: Improper Input Validation CWE-601: URL Redirection to Untrusted Site ('Open Redirect') •
CVSS: 6.1EPSS: 0%CPEs: 1EXPL: 0CVE-2020-15234 – Redirect URL matching ignores character casing
https://notcve.org/view.php?id=CVE-2020-15234
ORY Fosite is a security first OAuth2 & OpenID Connect framework for Go. In Fosite before version 0.34.1, the OAuth 2.0 Client's registered redirect URLs and the redirect URL provided at the OAuth2 Authorization Endpoint where compared using strings.ToLower while they should have been compared with a simple string match. This allows an attacker to register a client with allowed redirect URL https://example.com/callback. Then perform an OAuth2 flow and requesting redirect URL https://example.com/CALLBACK. Instead of an error (invalid redirect URL), the browser is redirected to https://example.com/CALLBACK with a potentially successful OAuth2 response, depending on the state of the overall OAuth2 flow (the user might still deny the request for example). • https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf https://github.com/ory/fosite/security/advisories/GHSA-grfp-q2mm-hfp6 • CWE-20: Improper Input Validation CWE-178: Improper Handling of Case Sensitivity CWE-601: URL Redirection to Untrusted Site ('Open Redirect') •
CVSS: 8.1EPSS: 0%CPEs: 1EXPL: 1CVE-2020-15222 – Replay of private_key_jwt possible in ORY Fosite
https://notcve.org/view.php?id=CVE-2020-15222
In ORY Fosite (the security first OAuth2 & OpenID Connect framework for Go) before version 0.31.0, when using "private_key_jwt" authentication the uniqueness of the `jti` value is not checked. When using client authentication method "private_key_jwt", OpenId specification says the following about assertion `jti`: "A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties". Hydra does not seem to check the uniqueness of this `jti` value. This problem is fixed in version 0.31.0. • https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9 https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43 https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication • CWE-287: Improper Authentication CWE-345: Insufficient Verification of Data Authenticity •
CVSS: 8.0EPSS: 0%CPEs: 1EXPL: 0CVE-2020-15223 – Ignored storage errors on token revokation in ORY Fosite
https://notcve.org/view.php?id=CVE-2020-15223
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 En ORY Fosite (el primer framework de seguridad OAuth2 & OpenID Connect para Go) anterior a la versión 0.34.0, el "TokenRevocationHandler" ignora los errores provenientes del almacenamiento. Esto puede conllevar a 200 códigos de estado no previstos que indican una revocación exitosa mientras el token aún es válido. • https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319 https://github.com/ory/fosite/security/advisories/GHSA-7mqr-2v3q-v2wm https://tools.ietf.org/html/rfc7009#section-2.2.1 • CWE-754: Improper Check for Unusual or Exceptional Conditions CWE-755: Improper Handling of Exceptional Conditions •