Bug 41814 - binutils: Multiple issues (ES 3.3)
binutils: Multiple issues (ES 3.3)
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: Security updates
UCS 3.3
Other Linux
: P3 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on: 41813
Blocks:
  Show dependency treegraph
 
Reported: 2016-07-18 14:38 CEST by Arvid Requate
Modified: 2019-04-11 19:23 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: 5.9 (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L)
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 2016-07-18 14:38:50 CEST
+++ This bug was initially created as a clone of Bug #41813 +++

Upstream Debian package version 2.22-8+deb7u3 fixes these issues:

* Exploitable buffer overflow (CVE-2016-2226)
* Invalid write due to a use-after-free to array btypevec (CVE-2016-4487)
* Invalid write due to a use-after-free to array ktypevec (CVE-2016-4488)
* Invalid write due to integer overflow (CVE-2016-4489)
* Write access violation (CVE-2016-4490)
* Write access violations (CVE-2016-4492)
* Read access violations (CVE-2016-4493)
* Bug 1352068 – CVE-2016-6131 gcc,gdb,binutils,libitm: Stack overflow vulnerability in libiberty demangler (CVE-2016-6131)
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:10:57 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.