Langflow up to 1.0.18 HTTP POST Request utils.py remaining_text redos
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Langflow up to 1.0.18 and classified as problematic. The impacted element is an unknown function of the file \src\backend\base\langflow\interface\utils.py of the component HTTP POST Request Handler. This manipulation of the argument remaining_text causes redos. The identification of this vulnerability is CVE-2024-9277. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability classified as problematic was found in Langflow up to 1.0.18. Affected by this vulnerability is an unknown part of the file \src\backend\base\langflow\interface\utils.py of the component HTTP POST Request Handler. The manipulation of the argument remaining_text with an unknown input leads to a redos vulnerability. The CWE definition for the vulnerability is CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. As an impact it is known to affect availability.
It is possible to read the advisory at rumbling-slice-eb0.notion.site. This vulnerability is known as CVE-2024-9277. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1449.003 according to MITRE ATT&CK.
It is possible to download the exploit at rumbling-slice-eb0.notion.site. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 1.0.0
- 1.0.1
- 1.0.2
- 1.0.3
- 1.0.4
- 1.0.5
- 1.0.6
- 1.0.7
- 1.0.8
- 1.0.9
- 1.0.10
- 1.0.11
- 1.0.12
- 1.0.13
- 1.0.14
- 1.0.15
- 1.0.16
- 1.0.17
- 1.0.18
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 3.5
CNA Vector: 🔍
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/27/2024 🔍09/27/2024 🔍
06/06/2025 🔍
Sources
Advisory: rumbling-slice-eb0.notion.siteStatus: Not defined
CVE: CVE-2024-9277 (🔍)
GCVE (CVE): GCVE-0-2024-9277
GCVE (VulDB): GCVE-100-278659
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/27/2024 07:37Updated: 06/06/2025 05:38
Changes: 09/27/2024 07:37 (56), 10/01/2024 06:48 (19), 06/06/2025 05:38 (23)
Complete: 🔍
Submitter: HRP_0
Cache ID: 216::103
Submit
Accepted
- Submit #410043: langflow-ai langflow <=v1.0.18 Redos (by HRP_0)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.