-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
x/vulndb: potential Go vuln in github.com/zitadel/zitadel: CVE-2023-44399 #2107
Labels
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
Comments
jba
added
NeedsReport
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
excluded: NOT_IMPORTABLE
This vulnerability only exists in a binary and is not importable.
and removed
NeedsReport
excluded: NOT_IMPORTABLE
This vulnerability only exists in a binary and is not importable.
labels
Oct 11, 2023
This is a real vuln with a fix in Go code. But tagging is off: the fix is in v2, but the module path does not end in v2. Running |
Change https://go.dev/cl/535696 mentions this issue: |
This was referenced Nov 8, 2023
Closed
This was referenced Nov 29, 2023
Closed
This was referenced Mar 11, 2024
Closed
This was referenced Mar 28, 2024
Closed
Closed
This was referenced Apr 25, 2024
Closed
Change https://go.dev/cl/592763 mentions this issue: |
This was referenced Jul 31, 2024
This was referenced Sep 19, 2024
Closed
This was referenced Sep 19, 2024
Closed
This was referenced Oct 25, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
CVE-2023-44399 references github.com/zitadel/zitadel, which may be a Go module.
Description:
ZITADEL provides identity infrastructure. In versions 2.37.2 and prior, ZITADEL administrators can enable a setting called "Ignoring unknown usernames" which helps mitigate attacks that try to guess/enumerate usernames. While this settings was properly working during the authentication process it did not work correctly on the password reset flow. This meant that even if this feature was active that an attacker could use the password reset function to verify if an account exist within ZITADEL. This bug has been patched in versions 2.37.3 and 2.38.0. No known workarounds are available.
References:
Cross references:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: