{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-2292 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-2292 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2292 is a low-severity vulnerability in n/a, published on 17 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-2292 and fix it if it is affected.\n\nWhat it is: CVE-2005-2292 is a low-severity vulnerability in n/a, published on 17 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-2292 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2005-2292/ (Markdown: https://insights.sbomify.com/CVE-2005-2292/index.md)","id":"CVE-2005-2292","markdown":"https://insights.sbomify.com/CVE-2005-2292/index.md","name":"CVE-2005-2292","record":{"aliases":["GHSA-vhm2-37q8-p9f4"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Oracle JDeveloper","requires_auth":"none","summary":"Local attackers can read cleartext passwords from configuration files in Oracle JDeveloper, leading to sensitive information disclosure.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jdeveloper","vendor":"oracle"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"Oracle JDeveloper 9.0.4, 9.0.5, and 10.1.2 stores cleartext passwords in (1) IDEConnections.xml, (2) XSQLConfig.xml and (3) settings.xml, which allows local users to obtain sensitive information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2005-2292","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2005"},"n_packages":0,"n_references":5,"next":{"headline":"Information disclosure in n/a","id":"CVE-2005-2293"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2005-2291"},"products":["n/a"],"published":"2005-07-17","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2016-3504","kev_date_added":null,"published":"2016-07-21"},{"cvss_score":8.2,"headline":"Information disclosure in JDeveloper","id":"CVE-2018-2711","kev_date_added":null,"published":"2018-01-18"},{"cvss_score":7.5,"headline":"Missing authorization in Oracle JDeveloper","id":"CVE-2026-60622","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":7.5,"headline":"Missing authorization in Oracle JDeveloper","id":"CVE-2026-60629","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":7.2,"headline":"Auth bypass in Oracle JDeveloper","id":"CVE-2026-60345","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":7,"headline":"Privilege escalation in Oracle JDeveloper","id":"CVE-2026-61061","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":6.5,"headline":"Information disclosure in Oracle JDeveloper","id":"CVE-2026-60350","kev_date_added":null,"published":"2026-07-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Local attackers can read cleartext passwords from configuration files in Oracle JDeveloper, leading to sensitive information disclosure.","url":"https://insights.sbomify.com/CVE-2005-2292/"}