Skip to content

User Registration Bypass in Zitadel

High severity GitHub Reviewed Published Oct 25, 2024 in zitadel/zitadel • Updated Oct 25, 2024

Package

gomod github.com/zitadel/zitadel (Go)

Affected versions

>= 2.63.0, < 2.63.5
>= 2.62.0, < 2.62.7
>= 2.61.0, < 2.61.4
>= 2.60.0, < 2.60.4
>= 2.59.0, < 2.59.5
< 2.58.7

Patched versions

2.63.5
2.62.7
2.61.4
2.60.4
2.59.5
2.58.7

Description

Impact

Zitadel allows administrators to disable the user self-registration. Due to a missing security check in versions prior to 2.63.4, disabling the "User Registration allowed" option only hid the registration button on the login page. Users could bypass this restriction by directly accessing the registration URL (/ui/login/loginname) and register a user that way.

Patches

2.x versions are fixed on >= 2.64.0
2.63.x versions are fixed on >= 2.63.5
2.62.x versions are fixed on >= 2.62.7
2.61.x versions are fixed on >= 2.61.4
2.60.x versions are fixed on >= 2.60.4
2.59.x versions are fixed on >= 2.59.5
2.58.x versions are fixed on >= 2.58.7

Workarounds

Updating to the patched version is the recommended solution.

Questions

If you have any questions or comments about this advisory, please email us at [email protected]

Credits

Thanks to @sevensolutions and @evilgensec for disclosing this!

References

@livio-a livio-a published to zitadel/zitadel Oct 25, 2024
Published by the National Vulnerability Database Oct 25, 2024
Published to the GitHub Advisory Database Oct 25, 2024
Reviewed Oct 25, 2024
Last updated Oct 25, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.083%
(36th percentile)

Weaknesses

CVE ID

CVE-2024-49757

GHSA ID

GHSA-3rmw-76m6-4gjc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.