Bug 41624

Summary: clamav: Multiple issues (3.3)
Product: UCS Reporter: Arvid Requate <requate>
Component: Security updatesAssignee: UCS maintainers <ucs-maintainers>
Status: CLOSED WONTFIX QA Contact: UCS maintainers <ucs-maintainers>
Severity: normal    
Priority: P5 CC: gohmann
Version: UCS 3.3Flags: requate: Patch_Available+
Target Milestone: UCS 3.3-0-errata   
Hardware: Other   
OS: Linux   
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.5 (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)
Bug Depends on: 41623    
Bug Blocks:    

Description Arvid Requate univentionstaff 2016-06-21 11:46:36 CEST
+++ This bug was initially created as a clone of Bug #41623 +++

The following issues have been fixed in ClamAV 0.99.2, a backport from Debian Jessie to Wheezy is expected:

* Crash when processing a crafted mew packer executable (CVE-2016-1371)
* Multiple vulnerabilities when processing crafted 7z files (CVE-2016-1372)

There's a couple of commits (~10) addressing these in the upstream repository, all committed under the clamav bug ID "11514".
Comment 1 Arvid Requate univentionstaff 2016-08-15 21:38:43 CEST
Upstream Debian package version 0.99.2+dfsg-0+deb7u2 updates the wheezy package to clamav 0.99.2.
Comment 2 Arvid Requate univentionstaff 2016-10-05 12:57:33 CEST
*** Bug 42564 has been marked as a duplicate of this bug. ***
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:11:27 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.