Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geeklog's Handling of Zip Files that have Files with Names not Compatible with the Web Servers OS #1101

Closed
eSilverStrike opened this issue Nov 8, 2021 · 2 comments
Assignees
Labels
Bug An issue describing unexpected or malicious behaviour.
Milestone

Comments

@eSilverStrike
Copy link
Member

This issue is a summary from a discussion found here: #1100 as reported by remyKobolski

It also is related somewhat to #1002

Before/while Geeklog extracts a zip file should we scan the file names to determine if they are all compatible with the current web server OS?

For example Windows Servers filenames can have ":" and Linux cannot.

Basically, unzipping the plugin should not allow to extract such files: skip files that begin with a dot, have unprintable names, or contains characters like ‘<‘, ‘>’, ‘!’, ‘?’.

If a file is found the extraction should be aborted since we have no idea if the file is actually required.

The main thing this affects is installing/updating plugins from a zip file.

The other option for this is we include a requirement for plugins that all filenames used are compatible with any OS of the Web servers Geeklog supports. We can state this in the Wiki (and what not to use). We already make other somewhat similar assumptions that the plugin zip file is setup in a certain way and contains certain files.

@eSilverStrike eSilverStrike added the Feature Issues that describe new features. label Nov 8, 2021
@eSilverStrike eSilverStrike added this to the 2.2.2 milestone Nov 8, 2021
@remyKobolski
Copy link

The signature of the extract method of the split brain package contains a optional preg string to match include files and same for files to exclude. That would be a option to use and document it.

mystralkk added a commit that referenced this issue Jan 10, 2022
@mystralkk
Copy link
Member

Fixed with change set 1627670. Now valid characters are [0-9a-zA-Z_.-].

@mystralkk mystralkk self-assigned this Jan 10, 2022
@eSilverStrike eSilverStrike added Bug An issue describing unexpected or malicious behaviour. and removed Feature Issues that describe new features. labels May 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug An issue describing unexpected or malicious behaviour.
Projects
None yet
Development

No branches or pull requests

3 participants