GHSA-4qpj-gxxg-jqg4 json
Swiftmailer Sendmail transport arbitrary shell execution
published 2y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Prior to 5.2.1, the sendmail transport (`Swift_Transport_SendmailTransport`) was vulnerable to an arbitrary shell execution if the "From" header came from a non-trusted source and no "Return-Path" is configured. This has been fixed in 5.2.1. If you are using sendmail as a transport, you are encouraged to upgrade as soon as possible.
Patch / fix
- packagist swiftmailer/swiftmailer 5.2.1
Is GHSA-4qpj-gxxg-jqg4 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | swiftmailer/swiftmailer | >=4.0.0, <5.2.1 |
5.2.1 |
References
-
github.com
/swiftmailer/swiftmailer/commit/b4b78af55e5e87f5ff07c06c6be7963c44562f80
web
-
github.com
/swiftmailer/swiftmailer/commit/efc430606a5faed864b969adfbdc5363ce2115a2
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/swiftmailer/swiftmailer/2014-06-13.yaml
web
-
github.com
/swiftmailer/swiftmailer
package
-
web.archive.org
/web/20150219063146/http://blog.swiftmailer.org/post/88660759928/security-fix-swiftmailer-5-2-1-released
web
-
blog.swiftmailer.org
/post/88660759928/security-fix-swiftmailer-5-2-1-released
web
Sources
- GitHub Advisory GHSA-4qpj-gxxg-jqg4
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.