Description
Path Traversal: '..\filename' in GitHub repository froxlor/froxlor prior to 2.0.0.
Basic information
- Type
- reviewed
- Severity
- medium
- Advisory on GitHub
- Open advisory ↗
- Repository advisory
- —
- Source code
- Browse source ↗
- Published (advisory)
- 2023-01-16 03:30:25 UTC
- Updated
- 2023-01-24 18:05:17 UTC
- GitHub reviewed
- 2023-01-19 18:24:42 UTC
- NVD published
- 2023-01-15
EPSS Score
| Score |
Percentile |
|
0.27%
|
49.69% |
CVSS Scores
| Base score |
Version |
Severity |
Vector |
|
5.5
|
3.1 |
—
|
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Click to expand
- Attack vector (AV:L)
- They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
- Attack complexity (AC:L)
- Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
- Privileges required (PR:L)
- A normal user session is enough; they don’t have to be admin.
- User interaction (UI:N)
- Nobody has to click “OK” or open a trap file; it can work without a victim helping.
- Scope (S:U)
- Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
- Confidentiality (C:H)
- Serious risk that confidential data gets exposed in a big way.
- Integrity (I:N)
- Data isn’t meaningfully altered or forged.
- Availability (A:N)
- Service keeps running; no real outage angle.
|
CWEs
| CWE id |
Name |
|
CWE-29
|
Path Traversal: '..filename' |
Affected packages (1)
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem |
Package |
Vulnerable range |
First patched |
Vulnerable functions |
| composer |
froxlor/froxlor |
< 2.0.0 |
2.0.0 |
—
|
cvelogic
Threat Intelligence