{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-2774 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-2774 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2774 is a medium-severity memory corruption vulnerability in n/a, published on 2 Sep 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-2774 and fix it if it is affected.\n\nWhat it is: CVE-2005-2774 is a medium-severity memory corruption vulnerability in n/a, published on 2 Sep 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-2774 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-2774/ (Markdown: https://insights.sbomify.com/CVE-2005-2774/index.md)","id":"CVE-2005-2774","markdown":"https://insights.sbomify.com/CVE-2005-2774/index.md","name":"CVE-2005-2774","record":{"aliases":["GHSA-2c5v-4pcw-67jx"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Quake 2 game mod","requires_auth":"none","summary":"Remote attackers can crash the Quake 2 server or execute arbitrary code via format string vulnerabilities in the nickname field of the Lithium II mod.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lithium_ii_mod","vendor":"lithium_software"}],"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":"Format string vulnerability in Lithium II mod 1.24 for Quake 2 allows remote attackers to cause a denial of service (server crash) and possibly execute arbitrary code via format string specifiers in the nickname.","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-2774","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2005"},"n_packages":0,"n_references":4,"next":{"headline":"Code injection in n/a","id":"CVE-2005-2775"},"packages":[],"prev":{"headline":"HP OpenView Network Node Manager Remote Code Execution","id":"CVE-2005-2773"},"products":["n/a"],"published":"2005-09-02","related":[],"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 Quake 2 server or execute arbitrary code via format string vulnerabilities in the nickname field of the Lithium II mod.","url":"https://insights.sbomify.com/CVE-2005-2774/"}