GHSA-45xg-4w5x-j429 json
TYPO3 Arbitrary Shell Execution in Swiftmailer library
published 2y ago modified last yr.
- cvss
- 8.1
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The swiftmailer library in use allows to execute arbitrary shell commands if the "From" header comes from a non-trusted source and no "Return-Path" is configured. Affected are only TYPO3 installation the configuration option ``` $GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport'] ``` is set to "sendmail". Installations with the default configuration are not affected.
Patch / fix
- packagist typo3/cms 4.5.37, 4.7.20, 6.1.12, 6.2.6
- github.com/TYPO3/typo3@313c4bb commit
- github.com/TYPO3/typo3@6af3757 commit
- github.com/TYPO3/typo3@dbdd9f2 commit
- github.com/TYPO3/typo3@ead183c commit
Is GHSA-45xg-4w5x-j429 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 FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms | >=6.2.0, <6.2.6 >=6.1.0, <6.1.12 >=4.7.0, <4.7.20 >=4.5.0, <4.5.37 |
6.2.6 6.1.12 4.7.20 4.5.37 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/TYPO3/typo3/commit/313c4bba53dd78803a9ee97c1f6f1d450a521521
web
-
github.com
/TYPO3/typo3/commit/6af37574e063929eaab066dd9920b1fa8815da12
web
-
github.com
/TYPO3/typo3/commit/dbdd9f22b7cebf43f2e4abdb2a6a8a9f32af8f61
web
-
github.com
/TYPO3/typo3/commit/ead183c5acf25b7e1121adee5a5860bd9b5f05a2
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2014-10-22-2.yaml
web
-
github.com
/TYPO3/typo3
package
-
typo3.org
/security/advisory/typo3-core-sa-2014-002
web
Sources
- GitHub Advisory GHSA-45xg-4w5x-j429
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.