Remote command injection when using sendmail email transport

published 2021-09-20 5y ago modified 2021-09-17 5y ago

cvss: 5.8; 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

### Impact

Sites using the `sendmail` transport as part of their `mail` config are vulnerable to remote command injection due to a [vulnerability](https://github.com/advisories/GHSA-48ww-j4fc-435p) in the `nodemailer` dependency.

Ghost defaults to the `direct` transport so this is only exploitable if the `sendmail` transport is explicitly used.

### Patches

Fixed in 4.15.0, all sites should upgrade as soon as possible.

### Workarounds

* Use an alternative email transport as described in the [docs](https://ghost.org/docs/config/#mail).

### For more information

If you have any questions or comments about this advisory:

* email us at security@ghost.org

Patch / fix

fixed in 1 links 1

npm ghost 4.15.0

github.com/TryGhost/Ghost@93e4b2e commit

Is GHSA-wfrj-qqc2-83cm 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 Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	5.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	ghost	<4.15.0	4.15.0

Classification

Weakness

CWE-88 Improper Neutralization of Argument Delimiters in a Command

References

Sources

GitHub Advisory GHSA-wfrj-qqc2-83cm

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.