CVE-2003-1588
First published: Mon Feb 08 2010(Updated: )
Sun Cluster 2.2, when HA-Oracle or HA-Sybase DBMS services are used, stores database credentials in cleartext in a cluster configuration file, which allows local users to obtain sensitive information by reading this file.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle Solaris Cluster | =2.2 | |
| =2.2 |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2003-1588?
CVE-2003-1588 is classified as a medium severity vulnerability due to the exposure of database credentials in cleartext.
How do I fix CVE-2003-1588?
To fix CVE-2003-1588, ensure that the database credentials are stored securely and avoid using cleartext storage in configuration files.
What types of systems are affected by CVE-2003-1588?
CVE-2003-1588 affects Sun Cluster version 2.2 when used with HA-Oracle or HA-Sybase DBMS services.
What information is exposed in CVE-2003-1588?
CVE-2003-1588 exposes sensitive database credentials that can be accessed by local users.
Who can exploit CVE-2003-1588?
Local users with access to the cluster configuration file can exploit CVE-2003-1588 to obtain sensitive information.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/weakness
- agent/description
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- agent/last-modified-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/event
- vendor/sun
- canonical/oracle solaris cluster
- version/oracle solaris cluster/2.2