Discourse up to 3.1.2/3.2.0.beta2 Quote full name redos
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Discourse up to 3.1.2/3.2.0.beta2. Impacted is an unknown function of the component Quote Handler. Performing a manipulation of the argument full name results in redos. This vulnerability was named CVE-2023-45806. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Discourse up to 3.1.2/3.2.0.beta2. This affects some unknown functionality of the component Quote Handler. The manipulation of the argument full name with an unknown input leads to a redos vulnerability. CWE is classifying the issue as CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. This is going to have an impact on availability. The summary by CVE is:
Discourse is an open source platform for community discussion. Prior to version 3.13 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches, if a user has been quoted and uses a `|` in their full name, they might be able to trigger a bug that generates a lot of duplicate content in all the posts they've been quoted by updating their full name again. Version 3.13 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches contain a patch for this issue. No known workaround exists, although one can stop the "bleeding" by ensuring users only use alphanumeric characters in their full name field.
The weakness was presented 11/10/2023. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-45806 since 10/13/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1449.003 for this issue.
Upgrading to version 3.1.3 or 3.2.0.beta3 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
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: RedosCWE: CWE-1333 / 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.1.3/3.2.0.beta3
Patch: github.com
Timeline
10/13/2023 🔍11/10/2023 🔍
11/10/2023 🔍
12/06/2023 🔍
Sources
Product: github.comAdvisory: 2ec25105179199cf80912bf011c18b8b870e1863
Status: Confirmed
CVE: CVE-2023-45806 (🔍)
GCVE (CVE): GCVE-0-2023-45806
GCVE (VulDB): GCVE-100-244953
Entry
Created: 11/10/2023 16:16Updated: 12/06/2023 09:21
Changes: 11/10/2023 16:16 (48), 12/06/2023 09:21 (14)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.