Bug 33500 – nspr: Integer overflow in memory allocation (3.2)

Bug 33500 - nspr: Integer overflow in memory allocation (3.2)


Summary:	nspr: Integer overflow in memory allocation (3.2)

Status:	CLOSED FIXED

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

Importance:	P3 normal (vote)
Target Milestone:	UCS 3.2-2
Assigned To:	Moritz Muehlenhoff
QA Contact:	Philipp Hahn

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-21 10:44 CET by Moritz Muehlenhoff
Modified:	2014-05-20 07:53 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	---
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:

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

2013-11-21 10:44:03 CET

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

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

CVE-2013-5607: Integer overflow in memory allocation

Comment 1 Moritz Muehlenhoff

2014-05-02 13:26:10 CEST

This issue was fixed with the update to Squeeze 6.0.9 (Bug 34588). The QA should ideally be made by the same person.

Comment 2 Philipp Hahn

2014-05-06 20:21:22 CEST

OK: aptitude install '?source-package(nspr)'
OK: nspr (4.8.6-1+squeeze1) squeeze-security; urgency=high
  * Fix CVE-2013-5607: integer overflow on 64 bit systems
OK: LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.1  /usr/lib/xulrunner-1.9.1/xulrunner-bin

Comment 3 Stefan Gohmann

2014-05-20 07:53:28 CEST

UCS 3.2-2 has been released:
 http://docs.univention.de/release-notes-3.2-2-en.html
 http://docs.univention.de/release-notes-3.2-2-de.html

If this error occurs again, please use "Clone This Bug".