You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2021. It is now read-only.
Indeed, colons are not allowed filenames on ntfs. But like, how is one supposed to run such a file on Windows anyway? If an attacker used that filename, it wouldn't run either.
Maybe that was a name that was given to the researcher that uploaded the file?
Either way, it's true, we should perhaps sanitize files in order to make them compliant to NTFS rules.
botherder
changed the title
generate random (uuid ?) filename on unpacking
File names with special characters are not going to execute on Windows
Aug 25, 2015
have a look:
https://malwr.com/analysis/MDlhZTQzMTg4Y2Q3NDNhNWE3OWMxODcwYjMxMDFkZjY/
filename "InvoiceFaker::Number.number(5)info_247694448826.exe" is valid for ext4, but is not valid for ntfs.
maybe some ntfs filename validation should be added or uuid filename instead of original ?
The text was updated successfully, but these errors were encountered: