Bug 43390 - postgresql-common: Multiple issues (4.1)
postgresql-common: Multiple issues (4.1)
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: Security updates
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on: 45753
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-21 18:11 CET by Arvid Requate
Modified: 2019-04-11 19:26 CEST (History)
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
requate: Patch_Available+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2017-01-21 18:11:32 CET
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 Arvid Requate univentionstaff 2017-11-20 15:55:14 CET
Upstream Debian package version 134wheezy6 fixes:

* It was discovered that the pg_ctlcluster, pg_createcluster andpg_upgradecluster commands handled symbolic links insecurely which could result in local denial of service by overwriting arbitrary files (CVE-2017-8806)
Comment 2 Arvid Requate univentionstaff 2018-04-17 15:56:52 CEST
This issue has been filed against UCS 4.1.

UCS 4.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

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