CVE-1999-0632
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 · uneditedThe RPC portmapper service is running.
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 · moderate confidenceThe RPC portmapper service (rpcbind/portmap) is exposed and running on the system, typically listening on port 111. This service maps RPC program numbers to network ports and can be used by remote attackers for reconnaissance to discover available RPC services and potential entry points.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Verify if port 111 is listeningRun 'netstat -an | grep 111' or 'ss -tlnp | grep 111' to see if port 111 is in LISTEN stateAffected if Port 111 shows as LISTEN on any interface (0.0.0.0:111 or :::111)
-
Identify the process bound to port 111Run 'lsof -i :111' or 'ss -tlnp | grep 111' to identify the process name (rpcbind, portmap, or similar)Affected if A process named rpcbind, portmap, or rpcbindd is bound to port 111
-
Check if RPC portmapper service is enabledOn Linux: 'systemctl status rpcbind' or 'systemctl status portmap'. On Solaris: 'svcs -x rpcbind'. On AIX: 'lssrc -s rpcbind'Affected if The rpcbind or portmap service shows as active or running
-
Confirm network exposure of the serviceFrom an external system or different network segment, run 'nc -zv <target-ip> 111' or 'nmap -p 111 <target-ip>' to test if port 111 is reachableAffected if Port 111 responds to external network probes (not filtered by firewall)
-
Check for RPC services registrationRun 'rpcinfo -p <localhost>' or 'rpcinfo -p <target-ip>' to enumerate registered RPC servicesAffected if rpcinfo returns a list of registered RPC program numbers and versions
A system is affected if the RPC portmapper service is running and listening on port 111, regardless of whether it is accessible externally, as this enables remote reconnaissance of available RPC services.
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 dataIf the RPC portmapper service is not required for business operations, disable or remove it. Otherwise, restrict access to port 111 through firewall rules or network segmentation to prevent unauthorized external enumeration.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0632 — 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-1999-0632 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