CVE-1999-0568
First published: Fri Jan 01 1999(Updated: )
rpc.admind in Solaris is not running in a secure mode.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle Solaris SPARC |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-1999-0568?
CVE-1999-0568 is categorized with a moderate severity due to its potential for unauthorized access.
How do I fix CVE-1999-0568?
To fix CVE-1999-0568, ensure that rpc.admind is configured to run in a secure mode and apply the latest patches provided by Oracle for Solaris.
What are the risks associated with CVE-1999-0568?
The risks associated with CVE-1999-0568 include possible unauthorized access to system resources and sensitive information.
Does CVE-1999-0568 affect all versions of Solaris?
CVE-1999-0568 specifically affects certain versions of Solaris that have rpc.admind running in an insecure mode.
How can I determine if my Solaris system is vulnerable to CVE-1999-0568?
You can determine if your Solaris system is vulnerable to CVE-1999-0568 by checking the configuration settings of rpc.admind and reviewing the system's patch level.
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/references
- agent/description
- agent/last-modified-date
- agent/author
- agent/softwarecombine
- agent/event
- agent/source
- agent/tags
- collector/nvd-historical
- vendor/sun
- vendor/solaris
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- collector/nvd-index
- canonical/oracle solaris sparc