Skip to content

PHPMailer untrusted code may be run from an overridden address validator

High severity GitHub Reviewed Published Jun 16, 2021 in PHPMailer/PHPMailer • Updated Feb 7, 2024

Package

composer phpmailer/phpmailer (Composer)

Affected versions

< 6.5.0

Patched versions

6.5.0

Description

If a function is defined that has the same name as the default built-in email address validation scheme (php), it will be called in default configuration as when no validation scheme is provided, the default scheme's callable php was being called. If an attacker is able to inject such a function into the application (a much bigger issue), it will be called whenever an email address is validated, such as when calling validateAddress().

Impact

Low impact – exploitation requires that an attacker can already inject code into an application, but it provides a trigger pathway.

Patches

This is patched in PHPMailer 6.5.0 by denying the use of simple strings as validator function names, which is a very minor BC break.

Workarounds

Inject your own email validator function.

References

Reported by Vikrant Singh Chauhan via huntr.dev.
CVE-2021-3603

For more information

If you have any questions or comments about this advisory:

References

@Synchro Synchro published to PHPMailer/PHPMailer Jun 16, 2021
Reviewed Jun 16, 2021
Published by the National Vulnerability Database Jun 17, 2021
Published to the GitHub Advisory Database Jun 22, 2021
Last updated Feb 7, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(65th percentile)

Weaknesses

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Learn more on MITRE.

Inclusion of Functionality from Untrusted Control Sphere

The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. Learn more on MITRE.

CVE ID

CVE-2021-3603

GHSA ID

GHSA-77mr-wc79-m8j3

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.