RPC service denial via idle connection exhaustion
Published Jul 20, 2022 · Updated May 5, 2025
Denial of service in libtirpc before 1.3.3rc1 allows remote attackers to stop RPC request handling through idle TCP connections. svc_run fails to expire idle connections or handle accept returning EMFILE, so descriptor exhaustion drives a tight accept loop that cannot process requests. The attack requires enough idle connections to reach the process file-descriptor limit; affected RPC services then stop handling requests.
Summary
What happened
Denial of service in libtirpc before 1.3.3rc1 allows remote attackers to stop RPC request handling through idle TCP connections. svc_run fails to expire idle connections or handle accept returning EMFILE, so descriptor exhaustion drives a tight accept loop that cannot process requests. The attack requires enough idle connections to reach the process file-descriptor limit; affected RPC services then stop handling requests.
The record
- CVE
- CVE-2021-46828
- Published
- Jul 20, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-835, CWE-755, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo