CVE-2003-1588
Sun Cluster 2.2, when HA-Oracle or HA-Sybase DBMS services are used, stores database credentials...
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.
Exploit likelihood
What each source reports
NVD Score used
1.9
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.
- Record
CVE-2003-1588- CVSS 2.0
- 1.9 Low
AV:L/AC:M/Au:N/C:P/I:N/A:N - Weakness
- CWE-255
- Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2003-1588- Updated
- 2026-11-02
EUVDEUVD-2003-1578 No score
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.
- Record
EUVD-2003-1578- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-9vh6-7j9m-vqpw No score
Sun Cluster 2.2, when HA-Oracle or HA-Sybase DBMS services are used, stores database credentials...
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.
- Record
GHSA-9vh6-7j9m-vqpw- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2003-1588 is a low vulnerability (CVSS 1.9) in Sun Cluster, published February 8, 2010. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.27%, the 19th percentile. No source names a fixed version.