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 •
CVSS: 5.8EPSS: 0%CPEs: 1EXPL: 0CVE-2020-5300 – Disallow replay of `private_key_jwt` by blacklisting JTIs in Hydra
https://notcve.org/view.php?id=CVE-2020-5300
In Hydra (an OAuth2 Server and OpenID Certified™ OpenID Connect Provider written in Go), before version 1.4.0+oryOS.17, when using client authentication method 'private_key_jwt' [1], 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 check the uniqueness of this `jti` value. Exploiting this vulnerability is somewhat difficult because: - TLS protects against MITM which makes it difficult to intercept valid tokens for replay attacks - The expiry time of the JWT gives only a short window of opportunity where it could be replayed This has been patched in version v1.4.0+oryOS.17 En Hydra (un OAuth2 Server y OpenID Certified™ OpenID Connect Provider escrito en Go), versiones anteriores a 1.4.0+oryOS.17, cuando se usa el método de autenticación del cliente `private_key_jwt` [1], la especificación OpenId dice lo siguiente sobre la afirmación `jti`: "Un identificador único para el token, que puede ser usado para impedir la reutilización del token. Estos tokens DEBEN solo ser usados una vez, a menos que las condiciones de reutilización sean negociadas entre las partes". • https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3 https://github.com/ory/hydra/releases/tag/v1.4.0 https://github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66 • CWE-294: Authentication Bypass by Capture-replay •
CVSS: 6.1EPSS: 0%CPEs: 129EXPL: 2CVE-2019-8400
https://notcve.org/view.php?id=CVE-2019-8400
ORY Hydra before v1.0.0-rc.3+oryOS.9 has Reflected XSS via the oauth2/fallbacks/error error_hint parameter. ORY Hydra, en versiones anteriores a la v1.0.0-rc.3+oryOS.9, tiene Cross-Site Scripting (XSS) reflejado mediante el parámetro error_hint en oauth2/fallbacks/error error_hint. • https://drive.google.com/file/d/1-25expUYVfK6vsiCmEabUCuelOP7aUDj/view?usp=drivesdk https://github.com/ory/hydra/blob/master/CHANGELOG.md#v100-rc3oryos9-2018-12-06 https://github.com/ory/hydra/commit/9b5bbd48a72096930af08402c5e07fce7dd770f3 https://hackerone.com/reports/456333 https://www.youtube.com/watch?v=RIyZLeKEC8E • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •