There is also no restriction about the file extension (e.g. by passing the name or filename of the mail attachment itself (from email headers), the input values never get sanitized by the package. Even if a developer passes a `$filename` into the `Attachment::save()` method, e.g. In this case, where no `$filename` gets passed into the `Attachment::save()` method, the package would use a series of unsanitized and insecure input values from the mail as fallback. Prerequisite for the vulnerability is that the script stores the attachments without providing a `$filename`, or providing an unsanitized `$filename`, in `src/Attachment::save(string $path, string $filename = null)`. An attacker can send an email with a malicious attachment to the inbox, which gets crawled with `webklex/php-imap` or `webklex/laravel-imap`. Every application that stores attachments with `Attachment::save()` without providing a `$filename` or passing unsanitized user input is affected by this attack. Prior to version 5.3.0, an unsanitized attachment filename allows any unauthenticated user to leverage a directory traversal vulnerability, which results in a remote code execution vulnerability. PHP-IMAP is a wrapper for common IMAP communication without the need to have the php-imap module installed / enabled. Editions other than Enterprise are also affected. Regular user privileges can be used to exploit this vulnerability. By using crafted requests, custom PHP code can be injected and executed through the Notes module because of missing input validation. An Unrestricted File Upload vulnerability has been identified in the Notes module.
In CloudPanel before 2.3.1, insecure file upload leads to privilege escalation and authentication bypass.įunadmin v3.3.2 and v3.3.3 are vulnerable to Insecure file upload via the plugins install.Īn issue was discovered in SugarCRM Enterprise before 11.0.6 and 12.x before 12.0.3.
0 kommentar(er)
