Bug 41566 – nspr: Multiple issues (3.3)

Bug 41566 - nspr: Multiple issues (3.3)


Summary:	nspr: 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:

URL:
Keywords:

Depends on:	41565
Blocks:
	Show dependency tree / graph

Reported:	2016-06-14 14:08 CEST by Arvid Requate
Modified:	2019-04-11 19:24 CEST (History)
CC List:	0 users

See Also:	41334
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:	6.8 (CVSS:2.0/AV:N/AC:M/Au:N/C:P/I:P/A:P)

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

2016-06-14 14:08:11 CEST

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

Upstream Debian package version 2:4.9.2-1+deb7u4 of nspr (NetScape Portable Runtime Library) fixes this issue:

* Memory allocation issue related to PR_*printf functions (CVE-2016-1951)

Comment 1 Arvid Requate

2016-11-05 20:44:26 CET

Upstream Debian package has bee updated to version 2:4.12-1+deb7u1 which fixes:


The Network Security Service (NSS) libraries uses environment variables to configure lots of things, some of which refer to file system locations. Others can be degrade the operation of NSS in various ways, forcing compatibility modes and so on.

Previously, these environment variables were not ignored SUID binaries. This version of NetScape Portable Runtime Library (NSPR) introduce a new API, PR_GetEnVSecure, to address this.

Both NSPR and NSS need to be upgraded to address this problem.

Comment 2 Stefan Gohmann

2019-01-03 07:11:13 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.