Ubuntu LinuxOperating system · Canonical
CVE-2015-7236
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse-after-free vulnerability in xprt_set_caller in rpcb_svc_com.c in rpcbind 0.2.1 and earlier allows remote attackers to cause a denial of service (daemon crash) via crafted packets, involving a PMAP_CALLIT code.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUse-after-free vulnerability in xprt_set_caller function in rpcb_svc_com.c in rpcbind versions 0.2.1 and earlier. Remote attackers can send crafted packets containing PMAP_CALLIT code to trigger a dangling pointer dereference, resulting in daemon crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ubuntu LinuxOperating system
= 12.04= 14.04= 15.04
Debian LinuxOperating system
= 7.0<= 0.2.1= 10= 11.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if rpcbind is installedRun 'dpkg -l rpcbind' on Debian/Ubuntu systems or 'rpm -q rpcbind' on Oracle Solaris to determine if the package is presentAffected if rpcbind is not installed means not affected; if installed, proceed to version check
-
Determine installed rpcbind versionRun 'rpcbind -v' or check package version with 'dpkg -s rpcbind' (Debian/Ubuntu) or 'rpm -qi rpcbind' (Solaris)Affected if Version is 0.2.1 or lower indicates the vulnerable version is installed
-
Verify if rpcbind is network-accessibleRun 'netstat -anp | grep -E "111|rpc"' or 'ss -anp | grep -E "111|rpc"' to check if rpcbind is listening on any network interfaceAffected if Service is bound to 0.0.0.0 or an external IP address makes the vulnerability remotely exploitable; listening on 127.0.0.1 only reduces exposure
-
Confirm rpcbind process is runningRun 'ps aux | grep rpcbind' to verify the daemon is activeAffected if Daemon is not running means the vulnerability is not currently exploitable, even if the vulnerable version is installed
A system is affected if rpcbind version 0.2.1 or earlier is installed AND the daemon is running and accessible on a network interface, allowing remote attackers to send crafted PMAP_CALLIT packets.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade rpcbind to a version newer than 0.2.1 that contains the patched code, or apply the upstream patch addressing the use-after-free in xprt_set_caller.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7236 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7236 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data