Discourse up to 3.2.2/3.3.0.beta2 Meta Tag cross site scripting

Summaryinfo

A vulnerability marked as problematic has been reported in Discourse up to 3.2.2/3.3.0.beta2. This impacts an unknown function of the component Meta Tag Handler. The manipulation leads to cross site scripting. This vulnerability is listed as CVE-2024-35234. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Discourse up to 3.2.2/3.3.0.beta2. It has been rated as problematic. This issue affects an unknown code of the component Meta Tag Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

Discourse is an open-source discussion platform. Prior to version 3.2.3 on the `stable` branch and version 3.3.0.beta3 on the `tests-passed` branch, an attacker can execute arbitrary JavaScript on users’ browsers by posting a specific URL containing maliciously crafted meta tags. This issue only affects sites with Content Security Polic (CSP) disabled. The problem has been patched in version 3.2.3 on the `stable` branch and version 3.3.0.beta3 on the `tests-passed` branch. As a workaround, ensure CSP is enabled on the forum.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-35234 since 05/14/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

Upgrading to version 3.2.3 or 3.3.0.beta3 eliminates this vulnerability. Applying the patch 26aef0c288839378b9de5819e96eac8cf4ea60fd is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Chat Software

Name

• Discourse

Version

• 3.2.0
• 3.2.1
• 3.2.2
• 3.3.0.beta1
• 3.3.0.beta2

License

• open-source

Website

• Product: https://github.com/discourse/discourse/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion