CVE-2024-41953 Zitadel improperly sanitizes HTML in emails and Console UI

Medium 4.3 Published Updated

Attackers can inject malicious HTML into emails and UI via unsanitized usernames, potentially bypassing security controls despite CSP mitigations.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2024-41953?

CVE-2024-41953 is a medium-severity cross-site scripting vulnerability in zitadel, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

Zitadel is an open source identity management system. ZITADEL uses HTML for emails and renders certain information such as usernames dynamically. That information can be entered by users or administrators. Due to a missing output sanitization, these emails could include malicious code. This may potentially lead to a threat where an attacker, without privileges, could send out altered notifications that are part of the registration processes. An attacker could create a malicious link, where the injected code would be rendered as part of the email. On the user's detail page, the username was also not sanitized and would also render HTML, giving an attacker the same vulnerability. While it was possible to inject HTML including javascript, the execution of such scripts would be prevented by most email clients and the Content Security Policy in Console UI. This vulnerability is fixed in 2.58.1, 2.57.1, 2.56.2, 2.55.5, 2.54.8 2.53.9, and 2.52.3.

Weakness: CWE-79

Which versions are affected by CVE-2024-41953?

19 open source packages ship an affected version, including github.com/zitadel/zitadel. It affects 1 product.

PackageAffectedFixed in
github.com/zitadel/zitadel GoAll versionsNone
github.com/zitadel/zitadel GoAll versions0.0.0-20240731122110-189505c80fa6
github.com/zitadel/zitadel GoAll versions0.0.0-20240731122110-189505c80fa6
github.com/zitadel/zitadel GoFrom 0.0.01.80.0-v2.20.0.20240731122110-189505c80fa6
github.com/zitadel/zitadel GoFrom 0.0.01.80.0-v2.20.0.20240731122110-189505c80fa6
github.com/zitadel/zitadel GoFrom 1.80.12.52.3
13 more packages
github.com/zitadel/zitadel GoFrom 1.80.12.52.3
github.com/zitadel/zitadel GoFrom 2.53.02.53.9
github.com/zitadel/zitadel GoFrom 2.53.02.53.9
github.com/zitadel/zitadel GoFrom 2.54.02.54.8
github.com/zitadel/zitadel GoFrom 2.54.02.54.8
github.com/zitadel/zitadel GoFrom 2.55.02.55.5
github.com/zitadel/zitadel GoFrom 2.55.02.55.5
github.com/zitadel/zitadel GoFrom 2.56.02.56.2
github.com/zitadel/zitadel GoFrom 2.56.02.56.2
github.com/zitadel/zitadel GoFrom 2.57.02.57.1
github.com/zitadel/zitadel GoFrom 2.57.02.57.1
github.com/zitadel/zitadel GoFrom 2.58.02.58.1
github.com/zitadel/zitadel GoFrom 2.58.02.58.1

Products include Zitadel Zitadel.

How do I fix CVE-2024-41953?

Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 0.0.0-20240731122110-189505c80fa6, 1.80.0-v2.20.0.20240731122110-189505c80fa6, 2.52.3 or 2.53.9.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2024-41953 being exploited?

There is no known exploitation of CVE-2024-41953 in the wild and no public exploit code.

Sources

Also known as GHSA-v333-7h2p-5fhv, GO-2024-3015.

Is CVE-2024-41953 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free