Discourse up to 3.0.0/3.1.0.beta1 Topic information disclosure
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability was found in Discourse up to 3.0.0/3.1.0.beta1 and classified as problematic. Affected by this issue is an unknown code block of the component Topic Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:
Discourse is an open-source discussion platform. Prior to version 3.0.1 of the `stable` branch and version 3.1.0.beta2 of the `beta` and `tests-passed` branches, the count of topics displayed for a tag is a count of all regular topics regardless of whether the topic is in a read restricted category or not. As a result, any users can technically poll a sensitive tag to determine if a new topic is created in a category which the user does not have excess to. In version 3.0.1 of the `stable` branch and version 3.1.0.beta2 of the `beta` and `tests-passed` branches, the count of topics displayed for a tag defaults to only counting regular topics which are not in read restricted categories. Staff users will continue to see a count of all topics regardless of the topic's category read restrictions.
The weakness was published 03/18/2023 as GHSA-2wvr-4x7w-v795. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2023-23622 since 01/16/2023. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
Upgrading to version 3.0.1 or 3.1.0.beta2 eliminates this vulnerability. Applying the patch 105fee978d73b0ec23ff814a09d1c0c9ace95164 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.
CVSSv3VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔒
CNA Base Score: 4.3
CNA Vector (GitHub, Inc.): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: Discourse 3.0.1/3.1.0.beta2
Timeline01/16/2023 CVE reserved
03/18/2023 +61 days Advisory disclosed
03/18/2023 +0 days VulDB entry created
04/11/2023 +24 days VulDB last update
CVE: CVE-2023-23622 (🔒)
EntryCreated: 03/18/2023 08:29 AM
Updated: 04/11/2023 02:41 PM
Changes: 03/18/2023 08:29 AM (52), 04/11/2023 02:41 PM (9)
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!
No comments yet. Languages: en.
Please log in to comment.