Bug 1456763 (CVE-2017-6891) - CVE-2017-6891 libtasn1: Stack-based buffer overflow in asn1_find_node()
Summary: CVE-2017-6891 libtasn1: Stack-based buffer overflow in asn1_find_node()
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-6891
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1456764 1456765 1456766
Blocks: 1456767
TreeView+ depends on / blocked
 
Reported: 2017-05-30 10:19 UTC by Adam Mariš
Modified: 2021-02-17 02:06 UTC (History)
27 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-26 02:41:30 UTC


Attachments (Terms of Use)

Description Adam Mariš 2017-05-30 10:19:00 UTC
Two errors in the "asn1_find_node()" function (lib/parser_aux.c) within GnuTLS libtasn1 version 4.10 can be exploited to cause a stacked-based buffer overflow by tricking a user into processing a specially crafted assignments file via the e.g. asn1Coding utility.

Upstream patch:

https://git.savannah.gnu.org/gitweb/?p=libtasn1.git;a=commit;h=5520704d075802df25ce4ffccc010ba1641bd484

Comment 1 Adam Mariš 2017-05-30 10:19:47 UTC
Created libtasn1 tracking bugs for this issue:

Affects: fedora-all [bug 1456765]


Created mingw-libtasn1 tracking bugs for this issue:

Affects: epel-7 [bug 1456766]
Affects: fedora-all [bug 1456764]

Comment 2 Doran Moppert 2017-06-26 02:38:56 UTC
This is Secunia SA76125.  There is some discussion on the upstream mailing list which supports the assessment that the security consequences here are minimal:  typically the overflowed field is provided as a constant by the developer, or parsed by libtasn1 from a ".asn" file (in which case the parser truncates names more than 64 characters).

https://lists.gnu.org/archive/html/htlp-libtasn1/2017-05/

Comment 3 Doran Moppert 2017-06-26 02:39:11 UTC
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/.


Note You need to log in before you can comment on or make changes to this bug.