OpenList vulnerabilities

OpenList is a file list program that supports multiple storage backends. Prior to 4.2.4, the OpenList search API uses a non-separator-aware strings.HasPrefix comparison as a path containment authorization check when authorizing globally indexed Bleve results against a restricted user's BasePath. When Bleve search is enabled, a restricted authenticated user can obtain sibling-path results that pass the prefix check.

OpenList before version 4.2.3 contains a vulnerability in the offline download feature that allows an unprivileged user to write files outside the temporary directory, potentially creating, truncating, or overwriting any file writable by the OpenList process. The vulnerability stems from a lack of containment check in the filename derived from the Content-Disposition header.

OpenList, a file list program that supports multiple storage, prior to 4.2.4 contains a vulnerability where share creation and update checks 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.

OpenList, a file list program that supports multiple storage, prior to 4.2.4, the authenticated /api/fs/batch_rename handler in server/handles/fsbatch.go authorizes only the source directory produced by user.JoinPath(req.SrcDir) and validates renameObject.NewName with checkRelativePath, but does not validate attacker-controlled renameObject.SrcName, supplied as src_name, before concatenating it with the authorized path and passing the result to fs.Rename. A user with rename permission can use traversal segments in src_name to make path normalization select a file outside the authorized directory and configured base path, resulting in cross-user file integrity loss, limited availability impact, and file-existence disclosure through success or error responses. This issue is fixed in version 4.2.4.