OpenList: Arbitrary File Read via Path Prefix Confusion in Share Creation API
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OpenListTeam | OpenList | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Openlistteam | Openlist |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-86cx-wwf4-phq4 | OpenList: Arbitrary File Read via Path Prefix Confusion in Share Creation API |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.402% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openlistteam
Openlistteam openlist |
|
| Vendors & Products |
Openlistteam
Openlistteam openlist |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenList a file list program that supports multiple storage. Prior to 4.2.4, the share creation and update checks in server/handles/sharing.go use strings.HasPrefix(requested_path, user.BasePath) without enforcing a directory separator boundary. An authenticated user with CanShare permission and a BasePath such as /base can submit a sibling path such as /base2/secret.txt, create a share for the out-of-scope file, and use the public share download or list handlers to read data outside the assigned directory. This issue is fixed in version 4.2.4. | |
| Title | OpenList: Arbitrary File Read via Path Prefix Confusion in Share Creation API | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|