Skip to content
Fencer Vulns
medium 5.3

CVE-2018-14621 json

An infinite loop vulnerability was found in libtirpc before version 1.0.2-rc2.

published 2018-08-30 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-6528

cvss
5.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

An infinite loop vulnerability was found in libtirpc before version 1.0.2-rc2. 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.

Patch / fix

  • libtirpc SLES for SAP 11 SP4, SLES 11 SP4, SLE Software Development Kit 11 SP4 0.2.1-1.13.6.1

suse advisories SUSE-SU-2018:3146-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-14621 updated cvss 5.3

libtirpc: Infinite loop in EMFILE case in svc_vc.c

  • Red Hat Ceph Storage 2 libntirpc Red Hat Ceph Storage 3 libntirpc Red Hat Enterprise Linux 6 libtirpc Red Hat Enterprise Linux 7 libtirpc Red Hat Enterprise Linux 8 libtirpc Red Hat OpenShift Enterprise 3 libtirpc
    +2 more products
    Red Hat Storage 3 libntirpc Red Hat Virtualization 4 libtirpc
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.26% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C

Affected products

  • [UNKNOWN] libtirpc

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.