LogicalDOC Community: Relative Path Traversal
CVE-2024-54449 is a high-severity relative path traversal vulnerability in LogicalDOC Community from LogicalDOC, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 9.1 as the first without the flaw, so updating LogicalDOC Community to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.61% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update LogicalDOC Community to 9.1 or a later version.
- Update LogicalDOC Enterprise to 9.1 or a later version.
- Update Logicaldoc to 9.1 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| LogicalDOC | LogicalDOC Community | before 9.1 | 9.1 |
| LogicalDOC | LogicalDOC Enterprise | before 9.1 | 9.1 |
| Logicaldoc | Logicaldoc | before 9.1 | 9.1 |
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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- 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.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (synopsys.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
The API used to interact with documents in the application contains two endpoints with a flaw that allows an authenticated attacker to write a file with controlled contents to an arbitrary location on the underlying file system. This can be used to facilitate RCE. An account with ‘read’ and ‘write’ privileges on at least one existing document in the application is required to exploit the vulnerability. Exploitation of this vulnerability would allow an attacker to run commands of their choosing on the underlying operating system of the web server running LogicalDOC.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Relative Path Traversal
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as.. that can resolve to a location that is outside of that directory.
How developers prevent this class of flaw
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- blackduck.com/blog/cyrc-advisory-logicaldoc.htmlThird Party Advisory
Other vulnerabilities in LogicalDOC Community
- 7.2 High severity
- 7.1 High severity
- 7.1 High severity
- 8.7 High severity
- 8.7 High severity
- 7.1 High severity
Recent Relative Path Traversal vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
- 9.9 Critical severity
Spotted an error? Tell us.