Bug 43391 – postgresql-common: Multiple issues (3.3)

Bug 43391 - postgresql-common: Multiple issues (3.3)


Summary:	postgresql-common: Multiple issues (3.3)

Status:	CLOSED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-01-21 18:12 CET by Arvid Requate
Modified:	2019-04-11 19:24 CEST (History)
CC List:	0 users

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):	Security
Max CVSS v3 score:	7.8 (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) NVD

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 Arvid Requate

2017-01-21 18:12:36 CET

+++ This bug was initially created as a clone of Bug #43390 +++

Upstream Debian package version 134wheezy5 fixes these issues:

* A symlink in /var/log/postgresql/ can be used by the "postgres" system user to write to arbitrary files on the filesystem the next time PostgreSQL is started by root (CVE-2016-1255)

* pg_upgradecluster does not properly upgrade databases that are owned by a non-login role (or group) (Debianbug 614374)

Comment 1 Stefan Gohmann

2019-01-03 07:10:53 CET

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

Customers still on UCS 3.3 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.