Skip to content
Heist/ feed
Back to feed
Medium

Ory Kratos's `highest_available` setting does not properly respect code + mfa credentials

Type: advisorySources: OSV

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 though that should be disallowed. An attacker would need to steal or guess a valid login OTP of a user who has only OTP for login enabled and who has an incorrect `available_aal` value stored, to exploit this vulnerability. All other aspects of the session (e.g. the session’s aal) are not impacted by this issue. On the Ory Network, only 0.00066% of registered users were affected by this issue, and most of those users appeared to be test users. Their respective AAL values have since been updated and they are no longer vulnerable to this attack. Version 1.3.0 is not affected by this issue. As a workaround, those who require MFA should disable the passwordless code login method. If that is not possible, check the sessions `aal` to identify if the user has `aal1` or `aal2`.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2024-45042
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 05:52 UTC · Revision 1

Source evidence

Ory Kratos's `highest_available` setting does not properly respect code + mfa credentials

core-osv · Original source

Published 26 Sept 2024, 17:04 UTC

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 though that should be disallowed. An attacker would need to steal or guess a valid login OTP of a user who has only OTP for login enabled and who has an incorrect `available_aal` value stored, to exploit this vulnerability. All other aspects of the session (e.g. the session’s aal) are not impacted by this issue. On the Ory Network, only 0.00066% of registered users were affected by this issue, and most of those users appeared to be test users. Their respective AAL values have since been updated and they are no longer vulnerable to this attack. Version 1.3.0 is not affected by this issue. As a workaround, those who require MFA should disable the passwordless code login method. If that is not possible, check the sessions `aal` to identify if the user has `aal1` or `aal2`.

osv:CVE-2024-45042
Complete source record
{
  "id": "7fda54dea61c1f7059c1ffab320b7b2e3d1287cbba840dbbb572e48e733dbbd7",
  "url": "https://osv.dev/vulnerability/CVE-2024-45042",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Ory Kratos's `highest_available` setting does not properly respect code + mfa credentials",
    "summary": "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 though that should be disallowed. An attacker would need to steal or guess a valid login OTP of a user who has only OTP for login enabled and who has an incorrect `available_aal` value stored, to exploit this vulnerability. All other aspects of the session (e.g. the session’s aal) are not impacted by this issue. On the Ory Network, only 0.00066% of registered users were affected by this issue, and most of those users appeared to be test users. Their respective AAL values have since been updated and they are no longer vulnerable to this attack. Version 1.3.0 is not affected by this issue. As a workaround, those who require MFA should disable the passwordless code login method. If that is not possible, check the sessions `aal` to identify if the user has `aal1` or `aal2`.",
    "evidence": "osv:CVE-2024-45042",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2024-45042",
      "aliases": [
        "CVE-2024-45042",
        "GHSA-wc43-73w7-x2f5",
        "GO-2024-3160"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/ory/kratos",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "0a49fd05245f179501b117163cd574786f287fe8"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "1.3.0"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StringRangeExpression"
                  },
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "1.3.0"
                      }
                    ],
                    "source": "DESCRIPTION"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v1.2.0",
            "v1.1.0",
            "v1.0.0",
            "v0.13.0",
            "v0.11.1",
            "v0.11.0",
            "v0.11.0-alpha.0.pre.2",
            "v0.10.1",
            "v0.10.0",
            "v0.9.0-alpha.3",
            "v0.9.0-alpha.2",
            "v0.9.0-alpha.1",
            "v0.8.3-alpha.1.pre.0",
            "v0.8.2-alpha.1",
            "v0.8.1-alpha.1",
            "v0.8.0-alpha.4.pre.0",
            "v0.8.0-alpha.3",
            "v0.8.0-alpha.2",
            "v0.8.0-alpha.1",
            "v0.7.6-alpha.1",
            "v0.7.5-alpha.1",
            "v0.7.4-alpha.1",
            "v0.7.3-alpha.1",
            "v0.7.1-alpha.1",
            "v0.7.0-alpha.1",
            "v0.6.3-alpha.1",
            "v0.6.2-alpha.1",
            "v0.6.1-alpha.1",
            "v0.6.0-alpha.2",
            "v0.6.0-alpha.1",
            "v0.5.5-alpha.1",
            "v0.5.4-alpha.1",
            "v0.5.3-alpha.1",
            "v0.5.2-alpha.1",
            "v0.5.1-alpha.1",
            "v0.5.0-alpha.1",
            "v0.4.6-alpha.1",
            "v0.4.5-alpha.1",
            "v0.4.4-alpha.1",
            "v0.4.3-alpha.1",
            "v0.4.2-alpha.1",
            "v0.4.0-alpha.1",
            "v0.3.0-alpha.1",
            "v0.2.1-alpha.1",
            "v0.2.0-alpha.2",
            "v0.1.1-alpha.1",
            "v0.1.0-alpha.6",
            "v0.1.0-alpha.5",
            "v0.1.0-alpha.4",
            "v0.1.0-alpha.3",
            "v0.1.0-alpha.2",
            "v0.1.0-alpha.1",
            "v0.0.3-alpha.15",
            "v0.0.3-alpha.14",
            "v0.0.3-alpha.13",
            "v0.0.3-alpha.12",
            "v0.0.3-alpha.11",
            "v0.0.3-alpha.10",
            "v0.0.3-alpha.9",
            "v0.0.3-alpha.8+oryOS.15",
            "v0.0.3-alpha.7",
            "v0.0.3-alpha.5",
            "v0.0.3-alpha.4",
            "v0.0.3-alpha.3",
            "v0.0.3-alpha.2",
            "v0.0.3-alpha.1",
            "v0.0.1-alpha.9",
            "v0.0.1-alpha.11",
            "v0.0.1-alpha.10+oryOS.15",
            "v0.0.2-alpha.1",
            "v0.0.1-alpha.8",
            "v0.0.1-alpha.7",
            "v0.0.1-alpha.6",
            "v0.0.1-alpha.5",
            "v0.0.1-alpha.3"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-45042.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.355974731Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/45xxx/CVE-2024-45042.json",
        "https://github.com/ory/kratos/security/advisories/GHSA-wc43-73w7-x2f5",
        "https://nvd.nist.gov/vuln/detail/CVE-2024-45042"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-287"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/45xxx/CVE-2024-45042.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2024-45042",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 492859,
  "published_at": "2024-09-26T17:04:59.235+00:00"
}