{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2009-2475 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2009-2475 is a high-severity vulnerability in n/a, published on 10 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-2475 and fix it if it is affected.\n\nWhat it is: CVE-2009-2475 is a high-severity vulnerability in n/a, published on 10 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2009-2475 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-2009-2475/ (Markdown: https://insights.sbomify.com/CVE-2009-2475/index.md)","id":"CVE-2009-2475","markdown":"https://insights.sbomify.com/CVE-2009-2475/index.md","name":"CVE-2009-2475","record":{"aliases":["GHSA-2vx8-fp5p-f94q"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java SE Runtime","requires_auth":"none","summary":"Attackers can obtain sensitive information via static variables in Java SE libraries, potentially exposing internal data to context-dependent attackers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"java_se","vendor":"sun"},{"product":"openjdk","vendor":"sun"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Sun Java SE 5.0 before Update 20 and 6 before Update 15, and OpenJDK, might allow context-dependent attackers to obtain sensitive information via vectors involving static variables that are declared without the final keyword, related to (1) LayoutQueue, (2) Cursor.predefined, (3) AccessibleResourceBundle.getContents, (4) ImageReaderSpi.STANDARD_INPUT_TYPE, (5) ImageWriterSpi.STANDARD_OUTPUT_TYPE, (6) the imageio plugins, (7) DnsContext.debug, (8) RmfFileReader/StandardMidiFileWriter.types, (9) AbstractSaslImpl.logger, (10) Synth.Region.uiToRegionMap/lowerCaseNameMap, (11) the Introspector class and a cache of BeanInfo, and (12) JAX-WS, a different vulnerability than CVE-2009-2673.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2009-2475","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2009"},"n_packages":0,"n_references":21,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2009-2476"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2009-2474"},"products":["n/a"],"published":"2009-08-10","related":[{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2009-2476","kev_date_added":null,"published":"2009-08-10"},{"cvss_score":10,"headline":"Security feature bypass in n/a","id":"CVE-2009-2689","kev_date_added":null,"published":"2009-08-10"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-2721","kev_date_added":null,"published":"2009-08-10"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-2722","kev_date_added":null,"published":"2009-08-10"},{"cvss_score":10,"headline":"Deserialization in n/a","id":"CVE-2009-2723","kev_date_added":null,"published":"2009-08-10"},{"cvss_score":9.3,"headline":"Race condition in n/a","id":"CVE-2009-2724","kev_date_added":null,"published":"2009-08-10"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"Attackers can obtain sensitive information via static variables in Java SE libraries, potentially exposing internal data to context-dependent attackers.","url":"https://insights.sbomify.com/CVE-2009-2475/"}