CVE-1999-0084: High severity Sun Nfs vulnerability
Certain NFS servers allow users to use mknod to gain privileges by creating a writable kmem device and setting the UID to 0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
NFS Utilsfrom your environment.If NFS services are not required, uninstall NFS Utils from affected hosts to eliminate the vulnerable component.
- Configuration
Disable the ability for clients to create device nodes via mknod on exported filesystems. Configure the NFS server and export options to prevent creation of device files so clients cannot create writable kmem devices or set UID to 0.
NFS server (NFS Utils) device node creation (mknod) = disabled - Compensating control
Restrict access to NFS exports to trusted hosts only (via export rules and firewall/ACLs), and ensure exported directories are not writable by untrusted users. Isolate NFS servers from untrusted networks to reduce exposure until a patch is available.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-0084?
CVE-1999-0084 has a high severity due to its potential for privilege escalation.
How do I fix CVE-1999-0084?
To fix CVE-1999-0084, ensure that the NFS server is configured securely and restrict access rights for the mknod command.
What systems are affected by CVE-1999-0084?
CVE-1999-0084 affects certain NFS servers, particularly those from Sun.
What is the exploit method for CVE-1999-0084?
The exploit method for CVE-1999-0084 involves using the mknod command to create a writable kmem device and changing the UID to 0.
Are there any workarounds for CVE-1999-0084?
Workarounds for CVE-1999-0084 include disabling mknod commands or restricting user permissions on the affected NFS servers.