phpmailer/phpmailer
Affected
- introduced
6.1.8, fixed6.4.1(ecosystem)
Fixed versions
6.4.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-phpmailer-2020-36326, BIT-wordpress-2020-36326, BIT-wordpress-multisite-2020-36326, CVE-2020-36326
Object injection in PHPMailer/PHPMailer
Impact
This is a reintroduction of an earlier issue (CVE-2018-19296) by an unrelated bug fix in PHPMailer 6.1.8. An external file may be unexpectedly executable if it is used as a path to an attachment file via PHP's support for .phar files. Exploitation requires that an attacker is able to provide an unfiltered path to a file to attach, or to trick calling code into generating one. See this article for more info.
Patches
This issue was patched in the PHPMailer 6.4.1 release. This release also implements stricter filtering for attachment paths; paths that look like *any* kind of URL are rejected.
Workarounds
Validate paths to loaded files using the same pattern as used in `isPermittedPath()` before using them in *any* PHP file function, such as file_exists. This method can't be used directly because it is protected, but you can implement the same thing in calling code. Note that this should be applied to *all* user-supplied paths passed into such functions; it's not a problem specific to PHPMailer.
Credit
This issue was found by Fariskhi Vidyan, reported and managed via Tidelift.
Critical Basis: The source's own band: CRITICAL
6.1.8, fixed 6.4.1 (ecosystem)6.4.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0