Use-after-free vulnerability in rpcbind

rpcbind Updated 02 Oct 2025

Summary

23/09/2015
N/A
Yes i
Unrated
Not published

DSA-3366-1: rpcbind - security update. Affects rpcbind versions < 0.2.0-8+deb7u1. Fixed in 0.2.0-8+deb7u1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

rpcbind is a server that converts RPC program numbers into universal addresses. It is commonly used in Unix-like systems to provide remote procedure call (RPC) services. The rpcbind server listens for incoming RPC requests and maps the program number in the request to a network address. This allows clients to locate and connect to the appropriate RPC server. However, a use-after-free vulnerability has been discovered in rpcbind, which can be exploited remotely to cause a denial of service (rpcbind crash).

Vulnerability Detail

The use-after-free vulnerability in rpcbind allows a remote attacker to trigger a crash by exploiting a flaw in the server's handling of RPC program numbers. By sending a specially crafted RPC request, the attacker can cause the rpcbind server to free a memory object and then attempt to access it later, leading to a crash. This vulnerability can be exploited remotely, without requiring authentication or user interaction. The impact of this vulnerability is a denial of service, as the rpcbind server crashes and becomes unresponsive.

How To Fix

Minimum fixed version

0.2.0-8+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade rpcbind

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the available security updates as soon as possible.

Conclusion

The use-after-free vulnerability in rpcbind can be exploited remotely to cause a denial of service. It is crucial to upgrade the rpcbind package to the patched version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for rpcbind →

Share this vulnerability

FAQ

rpcbind is a server that converts RPC program numbers into universal addresses. It is commonly used in Unix-like systems to provide remote procedure call (RPC) services.

A use-after-free vulnerability occurs when a program attempts to access memory that has already been freed. This can lead to crashes, memory corruption, and potentially remote code execution.

The use-after-free vulnerability in rpcbind can be exploited remotely by sending a specially crafted RPC request. By triggering the flaw in the server's handling of RPC program numbers, an attacker can cause the rpcbind server to crash.

The impact of this vulnerability is a denial of service (rpcbind crash). When exploited, the rpcbind server becomes unresponsive, affecting the availability of RPC services.

To fix this vulnerability, it is recommended to upgrade the rpcbind package to the patched version. For the oldstable distribution (wheezy), upgrade to version 0.2.0-8+deb7u1. For the stable distribution (jessie), upgrade to version 0.2.1-6+deb8u1.

Related vulnerabilities

Recent vulnerabilities recorded for rpcbind.

How To Fix

Minimum fixed version

0.2.0-8+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade rpcbind

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback