CVE-2023-46249 (Markdown, published 2023-10-31T16:15Z)
Description: value: authentik is an open-source Identity Provider. Prior to versions 2023.8.4 and 2023.10.2, when the default admin user has been deleted, it is potentially possible for an attacker to set the password of the default admin user without any authentication. authentik uses a blueprint to create the default admin user, which can also optionally set the default admin users' password from an environment variable. When the user is deleted, the `initial-setup` flow used to configure authentik after the first installation becomes available again. authentik 2023.8.4 and 2023.10.2 fix this issue. As a workaround, ensure the default admin user (Username `akadmin`) exists and has a password set. It is recommended to use a very strong password for this user, and store it in a secure location like a password manager. It is also possible to deactivate the user to prevent any logins as akadmin.
Severity: nan (CVSS v3 base score: 9.8)
Weakness: CWE-306 \u2014 Missing Authentication for Critical Function
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Repository: https://github.com/goauthentik/authentik
Files changed:
authentik/flows/migrations/0027_auto_20231028_1424.py
blueprints/default/flow-oobe.yaml
blueprints/system/bootstrap.yaml
website/docs/releases/2023/v2023.10.md
website/docs/security/GHSA-rjvp-29xq-f62w.md
website/sidebars.js
Commit message: security: fix oobe-flow reuse when akadmin is deleted (#7361)

Signed-off-by: Jens Langhammer <jens@goauthentik.io>

Vulnerable code:
  - model: authentik_blueprints.blueprintinstance
    identifiers:
      metadata:
        labels:
          blueprints.goauthentik.io/system-bootstrap: "true"
    state: absent

Fixed code:
# Generated by Django 4.2.6 on 2023-10-28 14:24

from django.apps.registry import Apps
from django.db import migrations
from django.db.backends.base.schema import BaseDatabaseSchemaEditor


def set_oobe_flow_authentication(apps: Apps, schema_editor: BaseDatabaseSchemaEditor):
    from guardian.shortcuts import get_anonymous_user

    Flow = apps.get_model("authentik_flows", "Flow")
    User = apps.get_model("authentik_core", "User")

    db_alias = schema_editor.connection.alias

    users = User.objects.using(db_alias).exclude(username="akadmin")
    try:
        users = users.exclude(pk=get_anonymous_user().pk)
    # pylint: disable=broad-except
    except Exception:  # nosec
        pass

    if users.exists():
        Flow.objects.filter(slug="initial-setup").update(authentication="require_superuser")


class Migration(migrations.Migration):
    dependencies = [
        ("authentik_flows", "0026_alter_flow_options"),
    ]

    operations = [
        migrations.RunPython(set_oobe_flow_authentication),
    ]
- attrs:
    expression: |
      # This policy ensures that the setup flow can only be
      # used one time
      from authentik.flows.models import Flow, FlowAuthenticationRequirement
      Flow.objects.filter(slug="initial-setup").update(
          authentication=FlowAuthenticationRequirement.REQUIRE_SUPERUSER,
      )
      return True
  id: policy-default-oobe-flow-set-authentication
  identifiers:
    name: default-oobe-flow-set-authentication
  model: authentik_policies_expression.expressionpolicy
  id: binding-login
- identifiers:
    order: 0
    policy: !KeyOf policy-default-oobe-flow-set-authentication
    target: !KeyOf binding-login
  model: authentik_policies.policybinding
-   \*: fix [GHSA-rjvp-29xq-f62w](../security/GHSA-rjvp-29xq-f62w), Reported by [@devSparkle](https://github.com/devSparkle)
# GHSA-rjvp-29xq-f62w

_Reported by [@devSparkle](https://github.com/devSparkle)_

## Potential Installation takeover when default admin user is deleted

### Summary

In the affected versions, when the default admin user has been deleted, it is potentially possible for an attacker to set the password of the default admin user without any authentication.

### Patches

authentik 2023.8.4 and 2023.10.2 fix this issue, for other versions the workaround can be used.

### Impact

authentik uses a blueprint to create the default admin user, which can also optionally set the default admin users' password from an environment variable. When the user is deleted, the `initial-setup` flow used to configure authentik after the first installation becomes available again.

### Workarounds

Ensure the default admin user (Username `akadmin`) exists and has a password set. It is recommended to use a very strong password for this user, and store it in a secure location like a password manager. It is also possible to deactivate the user to prevent any logins as akadmin.

### For more information

If you have any questions or comments about this advisory:

-   Email us at [security@goauthentik.io](mailto:security@goauthentik.io)
                "security/GHSA-rjvp-29xq-f62w",