{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-0875 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-0875 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-0875 is a medium-severity memory corruption vulnerability in n/a, published on 26 Mar 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-0875 and fix it if it is affected.\n\nWhat it is: CVE-2005-0875 is a medium-severity memory corruption vulnerability in n/a, published on 26 Mar 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-0875 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-0875/ (Markdown: https://insights.sbomify.com/CVE-2005-0875/index.md)","id":"CVE-2005-0875","markdown":"https://insights.sbomify.com/CVE-2005-0875/index.md","name":"CVE-2005-0875","record":{"aliases":["GHSA-rf2r-3p8v-h284"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Trillian instant messenger","requires_auth":"none","summary":"Remote attackers can crash the Trillian instant messenger application by sending a long string in an HTTP response header via a malicious web server.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"trillian","vendor":"cerulean_studios"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"Multiple buffer overflows in the Yahoo plug-in for Trillian 2.0, 3.0, and 3.1 allow remote web servers to cause a denial of service (application crash) via a long string in an HTTP 1.1 response header.","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":"Memory corruption in n/a","id":"CVE-2005-0875","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2005"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2005-0876"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2005-0874"},"products":["n/a"],"published":"2005-03-26","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-5401","kev_date_added":null,"published":"2008-12-09"},{"cvss_score":10,"headline":"Use after free in n/a","id":"CVE-2008-5402","kev_date_added":null,"published":"2008-12-09"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-5403","kev_date_added":null,"published":"2008-12-09"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2002-2390","kev_date_added":null,"published":"2007-10-31"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2008-2409","kev_date_added":null,"published":"2008-05-23"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2008-2008","kev_date_added":null,"published":"2008-04-29"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-3832","kev_date_added":null,"published":"2007-07-17"}],"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 crash the Trillian instant messenger application by sending a long string in an HTTP response header via a malicious web server.","url":"https://insights.sbomify.com/CVE-2005-0875/"}