Discourse up to 3.0.5/3.1.0.beta6 Invite race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Discourse up to 3.0.5/3.1.0.beta6. It has been classified as problematic. This impacts an unknown function of the component Invite Handler. Performing a manipulation results in race condition. This vulnerability is known as CVE-2023-37904. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in Discourse up to 3.0.5/3.1.0.beta6. This affects an unknown code block of the component Invite Handler. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality. The summary by CVE is:
Discourse is an open source discussion platform. Prior to version 3.0.6 of the `stable` branch and version 3.1.0.beta7 of the `beta` and `tests-passed` branches, more users than permitted could be created from invite links. The issue is patched in version 3.0.6 of the `stable` branch and version 3.1.0.beta7 of the `beta` and `tests-passed` branches. As a workaround, use restrict to email address invites.
The weakness was published 07/28/2023 as GHSA-6wj5-4ph2-c7qg. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2023-37904 since 07/10/2023. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 3.0.6 or 3.1.0.beta7 eliminates this vulnerability. Applying the patch 62a609ea2d0645a27ee8adbb01ce10a5e03a600b 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.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.8VulDB Meta Temp Score: 2.7
VulDB Base Score: 2.6
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.1
NVD Vector: 🔍
CNA Base Score: 2.6
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Discourse 3.0.6/3.1.0.beta7
Patch: 62a609ea2d0645a27ee8adbb01ce10a5e03a600b
Timeline
07/10/2023 🔍07/28/2023 🔍
07/28/2023 🔍
08/23/2023 🔍
Sources
Product: github.comAdvisory: GHSA-6wj5-4ph2-c7qg
Status: Confirmed
CVE: CVE-2023-37904 (🔍)
GCVE (CVE): GCVE-0-2023-37904
GCVE (VulDB): GCVE-100-235695
Entry
Created: 07/28/2023 21:52Updated: 08/23/2023 08:40
Changes: 07/28/2023 21:52 (50), 08/23/2023 08:40 (12)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.