How severe is CVE-2005-2291?

CVE-2005-2291 has a CVSS 2.0 base score of 4.6, rated medium severity.

Is CVE-2005-2291 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (40th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-2291?

CVE-2005-2291 primarily affects Oracle Jdeveloper. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-2291?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2005-2291 published?

CVE-2005-2291 was published on 2005-07-18 and last updated on 2026-06-16.

CVE-2005-2291

CVE-2005-2291 is a medium-severity vulnerability in Oracle Jdeveloper with a CVSS 2.0 base score of 4.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.6)
EPSS exploit prediction: 1% (40th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Jdeveloper
Published: 2005-07-18
Last modified: 2026-06-16

Description

Oracle JDeveloper 9.0.4, 9.0.5, and 10.1.2 passes the cleartext password as a parameter when starting sqlplus, which allows local users to gain sensitive information.

Frequently asked questions

What is CVE-2005-2291?: Oracle JDeveloper 9.0.4, 9.0.5, and 10.1.2 passes the cleartext password as a parameter when starting sqlplus, which allows local users to gain sensitive information.
How severe is CVE-2005-2291?: CVE-2005-2291 has a CVSS 2.0 base score of 4.6, rated medium severity.
Is CVE-2005-2291 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (40th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-2291?: CVE-2005-2291 primarily affects Oracle Jdeveloper. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-2291?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2005-2291 published?: CVE-2005-2291 was published on 2005-07-18 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:oracle:jdeveloper:9.0.4:*:*:*:*:*:*:*
cpe:2.3:a:oracle:jdeveloper:9.0.5:*:*:*:*:*:*:*
cpe:2.3:a:oracle:jdeveloper:10.1.2:*:*:*:*:*:*:*

More vulnerabilities in Oracle Jdeveloper

CVE-2018-14721 — Critical (CVSS 10.0): FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to conduct server-side request forgery (SSRF)…
CVE-2022-23305 — Critical (CVSS 9.8): By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be…
CVE-2020-10683 — Critical (CVSS 9.8): dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE…
CVE-2018-14720 — Critical (CVSS 9.8): FasterXML jackson-databind 2.x before 2.9.7 might allow attackers to conduct external XML entity (XXE) attacks by…
CVE-2018-14719 — Critical (CVSS 9.8): FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging…
CVE-2018-14718 — Critical (CVSS 9.8): FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging…

All CVEs affecting Oracle Jdeveloper →