Bug 37372 – heirloom-mailx: Multiple issues (ES 3.3)

Bug 37372 - heirloom-mailx: Multiple issues (ES 3.3)


Summary:	heirloom-mailx: Multiple issues (ES 3.3)

Status:	CLOSED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Security updates
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P3 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-12-17 09:08 CET by Moritz Muehlenhoff
Modified:	2019-04-11 19:25 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Security Issue
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:	3.6 (CVSS:2.0/AV:L/AC:L/Au:N/C:P/I:P/A:N)

Flags:	requate: Patch_Available+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Moritz Muehlenhoff

2014-12-17 09:08:17 CET

An undocumented feature in mailx (the implementation of the mail command)
allows the execution of arbitrary commands if the email address is obtained
from a remote source (CVE-2014-7844, CVE-2004-2771)

heirloom-mailx is not the default mail(1) command in UCS, a separate bug exists for bsd-mailx.

Comment 1 Arvid Requate

2015-05-07 17:41:44 CEST

Fixed in upstream Debian package version 12.4-2+deb6u1

Comment 2 Stefan Gohmann

2019-01-03 07:18:12 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.