dbcve.org
ZitadelApplication

CVE-2024-28855

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 2.41.15 / 2.42.15 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ZITADEL, open source authentication management software, uses Go templates to render the login UI. Due to a improper use of the `text/template` instead of the `html/template` package, the Login UI did not sanitize input parameters prior to versions 2.47.3, 2.46.1, 2.45.1, 2.44.3, 2.43.9, 2.42.15, and 2.41.15. An attacker could create a malicious link, where he injected code which would be rendered as part of the login screen. While it was possible to inject HTML including JavaScript, the execution of such scripts would be prevented by the Content Security Policy. Versions 2.47.3, 2.46.1, 2.45.1, 2.44.3, 2.43.9, 2.42.15, and 2.41.15 contain a patch for this issue. No known workarounds are available.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ZITADEL uses Go templates for login UI rendering. Due to using `text/template` instead of `html/template`, unsanitized input parameters are reflected in the login page. Attackers can inject HTML and JavaScript via malicious links, though Content Security Policy prevents script execution.

MitigationUpgrade to patched versions 2.47.3, 2.46.1, 2.45.1, 2.44.3, 2.43.9, 2.42.15, or 2.41.15. No workarounds are available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZitadelApplication
Affected:< 2.41.15>= 2.42.0, < 2.42.15>= 2.43.0, < 2.43.9>= 2.44.0, < 2.44.3>= 2.47.0, < 2.47.4= 2.45.0= 2.46.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ZITADEL version
    Run `zitadel version` from the ZITADEL binary, or check the Docker image tag, or query the ZITADEL API endpoint `/management/v1/version` or `/admin/v1/version`, or inspect the binary metadata using `file <path-to-zitadel-binary>` and compare to the version string in the binary.
    Affected if The installed version matches any of these vulnerable ranges: < 2.41.15; >= 2.42.0 and < 2.42.15; >= 2.43.0 and < 2.43.9; >= 2.44.0 and < 2.44.3; >= 2.47.0 and < 2.47.4; version 2.45.0; or version 2.46.0.
  2. Confirm ZITADEL login UI is exposed
    Access the ZITADEL login page URL (typically `/ui/login` or `/ui/login-password`) to verify the login UI is enabled and reachable.
    Affected if The login UI is accessible and the server responds with a login page rendered by ZITADEL.
  3. Check for XSS reflection in login parameters
    Craft a test URL with a malicious payload in a login flow parameter (such as `?username=<script>alert(1)</script>` or similar) and inspect the rendered HTML page source to see if the payload is reflected unsanitized.
    Affected if The input parameter value appears verbatim in the HTML response without encoding or sanitization, indicating `text/template` is being used instead of `html/template`.

A user is affected if their ZITADEL version falls within the vulnerable ranges listed and the login UI is exposed, allowing unsanitized input reflection in the rendered page.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.41.15 / 2.42.15 / 2.43.9 or later
Fixed in 2.41.152.42.152.43.9
Interim mitigation

Upgrade to patched versions 2.47.3, 2.46.1, 2.45.1, 2.44.3, 2.43.9, 2.42.15, or 2.41.15. No workarounds are available.

Recommended fix High confidence

2.47.3 (or any of: 2.41.15, 2.42.15, 2.43.9, 2.44.3, 2.45.1, 2.46.1)

  1. Identify the currently running Zitadel version
  2. Upgrade to one of the fixed versions: 2.41.15, 2.42.15, 2.43.9, 2.44.3, 2.45.1, 2.46.1, or 2.47.3
  3. Review Zitadel upgrade documentation for the chosen version
  4. Backup the Zitadel database before upgrading
  5. Perform the upgrade following official Zitadel upgrade procedures
  6. Verify the login UI renders correctly after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zitadel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28855 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28855 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data