langchain_experimental up to 0.0.60 Python REPL access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in langchain_experimental up to 0.0.60. Impacted is an unknown function of the component Python REPL Handler. The manipulation leads to access control. This vulnerability is uniquely identified as CVE-2024-38459. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in langchain_experimental up to 0.0.60. It has been rated as critical. This issue affects some unknown processing of the component Python REPL Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
langchain_experimental (aka LangChain Experimental) before 0.0.61 for LangChain provides Python REPL access without an opt-in step. NOTE; this issue exists because of an incomplete fix for CVE-2024-27444.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-38459 since 06/16/2024. The exploitation is known to be easy. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 0.0.61 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch ce0b0f22a175139df8f41cdcfb4d2af411112009 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 the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 0.0.1
- 0.0.2
- 0.0.3
- 0.0.4
- 0.0.5
- 0.0.6
- 0.0.7
- 0.0.8
- 0.0.9
- 0.0.10
- 0.0.11
- 0.0.12
- 0.0.13
- 0.0.14
- 0.0.15
- 0.0.16
- 0.0.17
- 0.0.18
- 0.0.19
- 0.0.20
- 0.0.21
- 0.0.22
- 0.0.23
- 0.0.24
- 0.0.25
- 0.0.26
- 0.0.27
- 0.0.28
- 0.0.29
- 0.0.30
- 0.0.31
- 0.0.32
- 0.0.33
- 0.0.34
- 0.0.35
- 0.0.36
- 0.0.37
- 0.0.38
- 0.0.39
- 0.0.40
- 0.0.41
- 0.0.42
- 0.0.43
- 0.0.44
- 0.0.45
- 0.0.46
- 0.0.47
- 0.0.48
- 0.0.49
- 0.0.50
- 0.0.51
- 0.0.52
- 0.0.53
- 0.0.54
- 0.0.55
- 0.0.56
- 0.0.57
- 0.0.58
- 0.0.59
- 0.0.60
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: langchain_experimental 0.0.61
Patch: ce0b0f22a175139df8f41cdcfb4d2af411112009
Timeline
06/16/2024 🔍06/16/2024 🔍
06/16/2024 🔍
06/17/2024 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2024-38459 (🔍)
GCVE (CVE): GCVE-0-2024-38459
GCVE (VulDB): GCVE-100-268757
Entry
Created: 06/16/2024 18:00Updated: 06/17/2024 14:21
Changes: 06/16/2024 18:00 (56), 06/17/2024 14:21 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.