REDHAT-BUG-2264106: High severity devfile registry-support vulnerability
This vulnerability affects https://github.com/devfile/registry-support and more specifically as part of a decompress function where we were reading archived files from a .tar and writing them to a new location. It was reported to us that the cleaning function we were using to ensure the file paths could not escape the directory they were supposed to go to was not working properly. This allowed somebody to potentially intercept the .tar file as it was being downloaded by the client and replace it with one that contained relative file paths. These paths when read by the decompress function would escape the destination directory and potentially overwrite arbitrary files.
The commit that contains the fix is here: https://github.com/devfile/registry-support/commit/0e44b9ca6d03fac4fc3f77d37656d56dc5defe0d
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2264106?
The severity of REDHAT-BUG-2264106 has not been specified but it involves potential security risks associated with file handling in the Devfile registry-support.
How do I fix REDHAT-BUG-2264106?
To fix REDHAT-BUG-2264106, ensure that you implement the latest patches or updates provided by the Devfile registry-support maintainers.
What does REDHAT-BUG-2264106 affect?
REDHAT-BUG-2264106 affects the decompress function in the Devfile registry-support when handling archived files from .tar.
When was REDHAT-BUG-2264106 reported?
REDHAT-BUG-2264106 was reported recently but the exact date is not specified in the provided information.
Is there a workaround for REDHAT-BUG-2264106?
There is no specific workaround mentioned for REDHAT-BUG-2264106, so updating to a fixed version is recommended.