<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: libtirpc project</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2021-46828: In libtirpc before 1.3.3rc1, remote attackers could exhaust the file descriptors of a process that uses libtir</title><link>https://patchthecve.com/cve/CVE-2021-46828.html</link><guid>https://patchthecve.com/cve/CVE-2021-46828.html</guid><pubDate>Wed, 14 Oct 2026 13:17:12 +0000</pubDate><description>HIGH 7.5: In libtirpc before 1.3.3rc1, remote attackers could exhaust the file descriptors of a process that uses libtirpc because idle TCP connections are mishandled. This can, in turn, lead to an svc_run infinite loop without accepting new connections.</description></item><item><title>CVE-2018-14622: A null-pointer dereference vulnerability was found in libtirpc before version 0.3.3-rc3</title><link>https://patchthecve.com/cve/CVE-2018-14622.html</link><guid>https://patchthecve.com/cve/CVE-2018-14622.html</guid><pubDate>Wed, 17 Jun 2026 01:41:18 +0000</pubDate><description>HIGH 7.5: A null-pointer dereference vulnerability was found in libtirpc before version 0.3.3-rc3. The return value of makefd_xprt() was not checked in all instances, which could lead to a crash when the server exhausted the maximum number of available file descriptors. A remote attacker could cause an rpc-ba</description></item><item><title>CVE-2018-14621: An infinite loop vulnerability was found in libtirpc before version 1.0.2-rc2</title><link>https://patchthecve.com/cve/CVE-2018-14621.html</link><guid>https://patchthecve.com/cve/CVE-2018-14621.html</guid><pubDate>Wed, 17 Jun 2026 01:41:18 +0000</pubDate><description>MEDIUM 5.3: 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.</description></item><item><title>CVE-2017-8779: rpcbind through 0.2.4, LIBTIRPC through 1.0.1 and 1.0.2-rc through 1.0.2-rc3, and NTIRPC through 1.4.3 do not </title><link>https://patchthecve.com/cve/CVE-2017-8779.html</link><guid>https://patchthecve.com/cve/CVE-2017-8779.html</guid><pubDate>Wed, 17 Jun 2026 01:26:56 +0000</pubDate><description>HIGH 7.5: rpcbind through 0.2.4, LIBTIRPC through 1.0.1 and 1.0.2-rc through 1.0.2-rc3, and NTIRPC through 1.4.3 do not consider the maximum RPC data size during memory allocation for XDR strings, which allows remote attackers to cause a denial of service (memory consumption with no subsequent free) via a cra</description></item><item><title>CVE-2013-1950: The svc_dg_getargs function in libtirpc 0.2.3 and earlier allows remote attackers to cause a denial of service</title><link>https://patchthecve.com/cve/CVE-2013-1950.html</link><guid>https://patchthecve.com/cve/CVE-2013-1950.html</guid><pubDate>Tue, 16 Jun 2026 23:52:27 +0000</pubDate><description>MEDIUM 4.3: The svc_dg_getargs function in libtirpc 0.2.3 and earlier allows remote attackers to cause a denial of service (rpcbind crash) via a Sun RPC request with crafted arguments that trigger a free of an invalid pointer.</description></item></channel></rss>