Discourse up to 3.0.5/3.1.0.beta6 Defer Queue resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Discourse up to 3.0.5/3.1.0.beta6. Affected by this issue is some unknown functionality of the component Defer Queue. The manipulation results in resource consumption. This vulnerability was named CVE-2023-38498. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Discourse up to 3.0.5/3.1.0.beta6. It has been classified as problematic. Affected is an unknown functionality of the component Defer Queue. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. CVE summarizes:
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, a malicious user can prevent the defer queue from proceeding promptly on sites hosted in the same multisite installation. 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. There are no known workarounds for this vulnerability. Users of multisite configurations should upgrade.
The weakness was presented 07/28/2023 as GHSA-wv29-rm3f-4g2j. The advisory is available at github.com. This vulnerability is traded as CVE-2023-38498 since 07/18/2023. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
Upgrading to version 3.0.6 or 3.1.0.beta7 eliminates this vulnerability. Applying the patch 26e267478d785e2f32ee7da4613e2cf4a65ff182 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 best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 4.3
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: Resource consumptionCWE: CWE-400 / CWE-404
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: 26e267478d785e2f32ee7da4613e2cf4a65ff182
Timeline
07/18/2023 🔍07/28/2023 🔍
07/28/2023 🔍
08/23/2023 🔍
Sources
Product: github.comAdvisory: GHSA-wv29-rm3f-4g2j
Status: Confirmed
CVE: CVE-2023-38498 (🔍)
GCVE (CVE): GCVE-0-2023-38498
GCVE (VulDB): GCVE-100-235698
Entry
Created: 07/28/2023 21:53Updated: 08/23/2023 08:48
Changes: 07/28/2023 21:53 (52), 08/23/2023 08:48 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.