{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2005-3904 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-3904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-3904 is a high-severity vulnerability in Sun Jdk, published on 30 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-3904 and fix it if it is affected.\n\nWhat it is: CVE-2005-3904 is a high-severity vulnerability in Sun Jdk, published on 30 Nov 2005. 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-2005-3904 in the wild and no public exploit code.\n\nAffected product: Sun Jdk. 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-3904/ (Markdown: https://insights.sbomify.com/CVE-2005-3904/index.md)","id":"CVE-2005-3904","markdown":"https://insights.sbomify.com/CVE-2005-3904/index.md","name":"CVE-2005-3904","record":{"aliases":["GHSA-r8qg-vjh8-h4m5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java Runtime Environment","requires_auth":"none","summary":"Remote attackers can bypass the Java sandbox to execute arbitrary code or access files, requiring immediate runtime upgrades.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jdk","vendor":"sun"},{"product":"jre","vendor":"sun"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Unspecified vulnerability in Java Management Extensions (JMX) in Java JDK and JRE 5.0 Update 3, 1.4.2 and later, 1.3.1 and later allows remote attackers to escape the Java sandbox and access arbitrary files or execute arbitrary application via unknown attack vectors.","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":"Security feature bypass in n/a","id":"CVE-2005-3904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"sun:jdk","products":["sun:jdk","sun:jre"],"type":"security_feature_bypass","year":"2005"},"n_packages":0,"n_references":14,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2005-3905"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2005-3903"},"products":["n/a"],"published":"2005-11-30","related":[{"cvss_score":10,"headline":"Deserialization in n/a","id":"CVE-2011-3521","kev_date_added":null,"published":"2011-10-19"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-3548","kev_date_added":null,"published":"2011-10-19"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-3549","kev_date_added":null,"published":"2011-10-19"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-3554","kev_date_added":null,"published":"2011-10-19"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-0802","kev_date_added":null,"published":"2011-06-14"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-0814","kev_date_added":null,"published":"2011-06-14"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-0815","kev_date_added":null,"published":"2011-06-14"}],"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":"Remote attackers can bypass the Java sandbox to execute arbitrary code or access files, requiring immediate runtime upgrades.","url":"https://insights.sbomify.com/CVE-2005-3904/"}