Bug 39441 – libidn: Multiple issues (3.2)

Bug 39441 - libidn: Multiple issues (3.2)


Summary:	libidn: Multiple issues (3.2)

Status:	CLOSED WONTFIX

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

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

URL:
Keywords:

Duplicates:	41950 (view as bug list)
Depends on:	42568
Blocks:
	Show dependency tree / graph

Reported:	2015-09-30 10:14 CEST 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:

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

2015-09-30 10:14:48 CEST

Fixed in upstream Debian package version 1.15-2+deb6u1:

* The stringprep_utf8_to_ucs4 function in libidn before 1.31, as used in jabberd2 and other applications, allows context-dependent attackers to read system memory and possibly have other unspecified impact via invalid UTF-8 characters in a string, which triggers an out-of-bounds read (CVE-2015-2059)

GNU Libidn is a fully documented implementation of the Stringprep, Punycode and IDNA specifications. Libidn's purpose is to encode and decode internationalized domain names.

Possibly affects gnutls, wget, and curl

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

Comment 1 Arvid Requate

2016-10-05 11:08:26 CEST

*** Bug 41950 has been marked as a duplicate of this bug. ***

Comment 2 Stefan Gohmann

2017-06-16 20:39:28 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 3 Stefan Gohmann

2017-08-08 07:11:18 CEST

This issue has been filed against UCS 3.2.

UCS 3.2 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.