CVSS: 4.6EPSS: 0%CPEs: 1EXPL: 0CVE-2024-45042 – Ory Kratos's `highest_available` setting does not properly respect code + mfa credentials
https://notcve.org/view.php?id=CVE-2024-45042
26 Sep 2024 — Ory Kratos is an identity, user management and authentication system for cloud services. Prior to version 1.3.0, given a number of preconditions, the `highest_available` setting will incorrectly assume that the identity’s highest available AAL is `aal1` even though it really is `aal2`. This means that the `highest_available` configuration will act as if the user has only one factor set up, for that particular user. This means that they can call the settings and whoami endpoint without a `aal2` session, even... • https://github.com/ory/kratos/security/advisories/GHSA-wc43-73w7-x2f5 • CWE-287: Improper Authentication •
CVSS: 7.5EPSS: 0%CPEs: 12EXPL: 0CVE-2021-32701 – Possible bypass of token claim validation when OAuth2 Introspection caching is enabled
https://notcve.org/view.php?id=CVE-2021-32701
22 Jun 2021 — ORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. When you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introsp... • https://github.com/ory/oathkeeper/commit/1f9f625c1a49e134ae2299ee95b8cf158feec932 • CWE-863: Incorrect Authorization •
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
02 Oct 2020 — 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 wh... • https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf • 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
02 Oct 2020 — 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. In... • https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf • 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
24 Sep 2020 — 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 doe... • https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9 • 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
24 Sep 2020 — 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 ... • https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319 • 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
06 Apr 2020 — 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 vulne... • https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3 • 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
17 Feb 2019 — 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 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •