Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1620290 - (CVE-2018-14621) CVE-2018-14621 libtirpc: Infinite loop in EMFILE case in svc_vc.c
CVE-2018-14621 libtirpc: Infinite loop in EMFILE case in svc_vc.c
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20160303,reported=2...
: Security
Depends On:
Blocks: 1620296
  Show dependency treegraph
 
Reported: 2018-08-22 17:46 EDT by Laura Pardo
Modified: 2018-09-20 02:34 EDT (History)
26 users (show)

See Also:
Fixed In Version: libtirpc 1.0.2-rc2
Doc Type: If docs needed, set a value
Doc Text:
An infinite loop vulnerability was found in libtirpc. With the port to using poll rather than select, exhaustion of file descriptors would cause the server to enter an infinite loop, consuming a large amount of CPU time and denying service to other clients until restarted.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Laura Pardo 2018-08-22 17:46:07 EDT
A flaw was found in libtirpc before version 1.0.2-rc2. With the port to poll, and endless loop can be created when running out of file descriptors.


References:
https://bugzilla.novell.com/show_bug.cgi?id=968175

Upstream Patch:
http://git.linux-nfs.org/?p=steved/libtirpc.git;a=commit;h=fce98161d9815ea016855d9f00274276452c2c4b
Comment 1 Doran Moppert 2018-08-22 22:55:52 EDT
This was introduced with the port to using poll() instead of select() around 0.3.3.  Prior versions use a different strategy when EMFILE/ENFILE is hit:  the "most idle" connection is dropped before retrying.

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