Discourse up to 3.0.0/3.1.0.beta1 Tag exclude_tag information disclosure

Summaryinfo

A vulnerability marked as problematic has been reported in Discourse up to 3.0.0/3.1.0.beta1. This issue affects some unknown processing of the component Tag Handler. This manipulation of the argument exclude_tag causes information disclosure. This vulnerability is registered as CVE-2023-23624. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Discourse up to 3.0.0/3.1.0.beta1 and classified as problematic. Affected by this vulnerability is an unknown code of the component Tag Handler. The manipulation of the argument exclude_tag with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

Discourse is an open-source discussion platform. Prior to version 3.0.1 on the `stable` branch and version 3.1.0.beta2 on the `beta` and `tests-passed` branches, someone can use the `exclude_tag param` to filter out topics and deduce which ones were using a specific hidden tag. This affects any Discourse site using hidden tags in public categories. This issue is patched in version 3.0.1 on the `stable` branch and version 3.1.0.beta2 on the `beta` and `tests-passed` branches. As a workaround, secure any categories that are using hidden tags, change any existing hidden tags to not include private data, or remove any hidden tags currently in use.

The weakness was published 01/28/2023 as GHSA-qgj5-g5vf-fm7q. The advisory is shared at github.com. This vulnerability is known as CVE-2023-23624 since 01/16/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 3.0.1 or 3.1.0.beta2 eliminates this vulnerability. Applying the patch f55e0fe7910149c431861c18ce407d1be0d6091a 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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Chat Software

Name

• Discourse

Version

• 3.0
• 3.1.0.beta1

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion