{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4765 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4765 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4765 is a high-severity vulnerability in Bea Weblogic Server, published on 1 Apr 2006. 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-4765 and fix it if it is affected.\n\nWhat it is: CVE-2005-4765 is a high-severity vulnerability in Bea Weblogic Server, published on 1 Apr 2006. 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-4765 in the wild and no public exploit code.\n\nAffected product: Bea Weblogic Server. 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-4765/ (Markdown: https://insights.sbomify.com/CVE-2005-4765/index.md)","id":"CVE-2005-4765","markdown":"https://insights.sbomify.com/CVE-2005-4765/index.md","name":"CVE-2005-4765","record":{"aliases":["GHSA-xcwx-pcf9-m967"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"WebLogic Server","requires_auth":"none","summary":"Remote attackers can sniff sensitive data from WebLogic deployments because the system fails to enforce secure t3s protocol even when configured.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"weblogic_server","vendor":"bea"}],"cvss":{"score":7.6,"severity":"high","source":"nvd","vector":"AV:N/AC:H/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"BEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier and 7.0 SP6 and earlier, when using the weblogic.Deployer command with the t3 protocol, does not use the secure t3s protocol even when an Administration port is enabled on the Administration server, which might allow remote attackers to sniff the connection.","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":"Information disclosure in n/a","id":"CVE-2005-4765","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"bea:weblogic_server","products":["bea:weblogic_server"],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2005-4766"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2005-4764"},"products":["n/a"],"published":"2006-04-01","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-3257","kev_date_added":null,"published":"2008-07-22"},{"cvss_score":10,"headline":"BEA WebLogic Server 7.0 through 7.0 SP7, 8.1 through 8.1 SP5, 9.0, and 9.1, when using the WebLogic Server 6.1 compatibility realm, allows a","id":"CVE-2007-0417","kev_date_added":null,"published":"2007-01-23"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2003-0640","kev_date_added":null,"published":"2003-08-02"},{"cvss_score":10,"headline":"Path traversal in n/a","id":"CVE-2001-0098","kev_date_added":null,"published":"2001-02-02"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2000-0681","kev_date_added":null,"published":"2000-10-13"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2000-0684","kev_date_added":null,"published":"2000-10-13"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2000-0685","kev_date_added":null,"published":"2000-10-13"}],"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-09-17","vendors":["n/a"]},"summary":"Remote attackers can sniff sensitive data from WebLogic deployments because the system fails to enforce secure t3s protocol even when configured.","url":"https://insights.sbomify.com/CVE-2005-4765/"}