CVE-2000-0032: Critical severity Sun SunOS vulnerability
Solaris dmicmd allows local users to crash the dmispd daemon by adding a malformed file to the /var/dmi/db database.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
Oracle Solaris dmi_cmdfrom your environment.If dmi_cmd is not required, uninstall or remove the dmi_cmd utility to prevent local users from using it to add malformed files that crash dmispd.
- Configuration
Restrict filesystem permissions on /var/dmi/db so that local unprivileged users cannot create or modify files there (ensure only root or designated administrative accounts have write access).
/var/dmi/db (DMI database) filesystem permissions (write) = remove write access for unprivileged users; allow only root or designated admin accounts - Compensating control
Stop and disable the dmispd daemon if DMI functionality is not required, or otherwise restrict local user access to systems that can write to /var/dmi/db until a vendor fix is available.
- Operational
Audit the /var/dmi/db directory for recently added or malformed files and remove or quarantine any suspicious entries; monitor logs for dmispd crashes or anomalous activity by local users.
Event History
Frequently Asked Questions
What is the severity of CVE-2000-0032?
CVE-2000-0032 is considered a low severity vulnerability that allows local users to crash the dmispd daemon.
How do I fix CVE-2000-0032?
To fix CVE-2000-0032, ensure that only authorized users have access to modify files in the /var/dmi/db directory.
What systems are affected by CVE-2000-0032?
CVE-2000-0032 affects Solaris 7.0 and SunOS 5.7 systems specifically.
Can CVE-2000-0032 be exploited remotely?
CVE-2000-0032 cannot be exploited remotely as it requires local user access to the system.
What are the potential impacts of CVE-2000-0032?
The main impact of CVE-2000-0032 is the denial of service caused by the crashing of the dmispd daemon.