CVE-2007-5462
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 · uneditedUnspecified vulnerability in the Sun Solaris RPC services library (librpcsvc) on Solaris 8 through 10 allows remote attackers to cause a denial of service (mountd crash) via unspecified packets to a server that exports many filesystems, and allows local users to cause a denial of service (automountd crash) via unspecified requests to mount filesystems from a server that exports many filesystems.
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 confidenceA denial of service vulnerability exists in the Sun Solaris librpcsvc library affecting Solaris 8 through 10. Remote attackers can crash mountd by sending unspecified packets to servers exporting many filesystems, while local users can crash automountd via unspecified filesystem mount requests from servers exporting many filesystems. The exact vulnerability mechanism is not specified in the available description.
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= 8.0= 9.0= 10.0CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 Solaris versionRun 'uname -a' or 'cat /etc/release' to determine the installed Solaris version. Look for 8.0, 9.0, or 10.0 in the output.Affected if The system runs Solaris 8, 9, or 10.
-
Verify if mountd RPC service is runningRun 'rpcinfo -p localhost' or 'rpcinfo -p' and look for program number 100005 (mountd) in the output. Alternatively, check if the process 'rpc.mountd' is running using 'ps -ef | grep mountd'.Affected if The mountd RPC service (program 100005) is actively running on the system.
-
Verify if automountd service is runningOn Solaris 10, run 'svcs -a | grep automount' to check service status. On older versions, check for 'automountd' processes using 'ps -ef | grep automount'.Affected if The automountd daemon is actively running on the system.
-
Check RPC service exposure (if remotely exploitable)Run 'rpcinfo -p' to list all registered RPC services. For remote attack vector, verify that mountd is bound to a network-exposed port and accessible from network.Affected if Mountd is network-exposed and the system accepts RPC connections from untrusted networks.
The system is vulnerable if it runs Solaris 8, 9, or 10 AND has either mountd or automountd services actively running, with mountd exposure to network attack vectors for remote DoS.
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 dataApply Oracle Solaris patches for this vulnerability; if patches are unavailable for end-of-life Solaris versions, consider upgrading to a supported OS release or disabling/restricting RPC mountd and automountd services if not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5462 — 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-2007-5462 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