Bug 1302622 (CVE-2016-2090)

Summary: CVE-2016-2090 libbsd: heap buffer overflow in fgetwln function
Product: [Other] Security Response Reporter: Andrej Nemec <anemec>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: spacewar
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=low,public=20160127,reported=20160127,source=oss-security,cvss2=2.6/AV:N/AC:H/Au:N/C:N/I:N/A:P,cwe=CWE-122,fedora-all/libbsd=affected,epel-5/libbsd=affected,epel-6/libbsd=affected,epel-7/libbsd=affected
Fixed In Version: libbsd 0.8.2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-08 02:47:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 1302623, 1302624, 1302625, 1302626    
Bug Blocks:    

Description Andrej Nemec 2016-01-28 09:58:04 UTC
libbsd 0.8.1 and earlier contains a buffer overflow in the function
fgetwln(). An if checks if it is necessary to reallocate memory in the
target buffer. However this check is off by one, therefore an out of
bounds write happens.

Original bug report

https://bugs.freedesktop.org/show_bug.cgi?id=93881

Upstream fix:

http://cgit.freedesktop.org/libbsd/commit/?id=c8f0723d2b4520bdd6b9eb7c3e7976de726d7ff7

External reference:

https://blog.fuzzing-project.org/36-Heap-buffer-overflow-in-fgetwln-function-of-libbsd.html

CVE assignment:

http://seclists.org/oss-sec/2016/q1/234

Comment 1 Andrej Nemec 2016-01-28 09:58:50 UTC
Created libbsd tracking bugs for this issue:

Affects: fedora-all [bug 1302623]
Affects: epel-5 [bug 1302624]
Affects: epel-6 [bug 1302625]
Affects: epel-7 [bug 1302626]

Comment 2 Product Security DevOps Team 2019-06-08 02:47:59 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.