Bug 1377926 (CVE-2016-8687)
Summary: | CVE-2016-8687 libarchive: stack based buffer overflow in bsdtar_expand_char (util.c) | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Doran Moppert <dmoppert> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | anto.trande, besser82, ndevos, praiskup, slawomir, trepik, yozone |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libarchive 3.2.2 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-23 03:20:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1378666, 1385674, 1385675, 1385676 | ||
Bug Blocks: | 1376684, 1385672 |
Description
Doran Moppert
2016-09-21 03:33:17 UTC
This only affects the bsdtar utility, libraries and applications linked against libarchive are not affected by this flaw. Compiling with -fstack-protector-strong (as is the case in RHEL & Fedora) mitigates any code execution vector here. In any case, the overflowed bytes are limited to ASCII octal escapes so even without these protections an attacker would need to be incredibly lucky to achieve more than a crash. Created libarchive tracking bugs for this issue: Affects: fedora-all [bug 1378666] Statement: Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. *** Bug 1385659 has been marked as a duplicate of this bug. *** |