parisneo/lollms-webui: Path Traversal: '..filename'
CVE-2024-3435 is a high-severity path traversal: '..filename' vulnerability in parisneo/lollms-webui from ParisNeo, with a CVSS 3.0 base score of 8.4 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 9.5 as the first without the flaw, so updating parisneo/lollms-webui to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.83% chance of exploitation within 30 days, higher than 58% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update parisneo/lollms-webui to 9.5 or a later version.
- Update lollms-webui to 9.5 or a later version.
- Update Lollms Web UI to 9.5 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Parisneo | parisneo/lollms-webui | before 9.5 | 9.5 |
| Parisneo | lollms-webui | before 9.5 | 9.5 |
| Lollms | Lollms Web UI | before 9.5 | 9.5 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (huntr.dev).
Official description
A path traversal vulnerability exists in the 'save_settings' endpoint of the parisneo/lollms-webui application, affecting versions up to the latest release before 9.5. The vulnerability arises due to insufficient sanitization of the 'config' parameter in the 'apply_settings' function, allowing an attacker to manipulate the application's configuration by sending specially crafted JSON payloads. This could lead to remote code execution (RCE) by bypassing existing patches designed to mitigate such vulnerabilities.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Path Traversal: '..filename'
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '..filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.
How developers prevent this class of flaw
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/parisneo/lollms-webui/commit/bb99b59e710d00c4f2598faa5e183fa30fbd3bc2
- huntr.com/bounties/494f349a-8650-4d30-a0bd-4742fda44ce5Exploit, Issue Tracking, Third Party Advisory
Other vulnerabilities in parisneo/lollms-webui
- 9.6 Critical severity
- 7.5 High severity
- 8.8 High severity
- 8.4 High severity
- 9.8 Critical severity
- 9.1 Critical severity
Recent Path Traversal: '..filename' vulnerabilities
- 7.5 High severity
- 9.6 Critical severity
- 9.8 Critical severity
- 8.6 High severity
- 9.9 Critical severity
- 7.5 High severity
Spotted an error? Tell us.