{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-1853 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2005-1853 is a high-severity vulnerability in n/a, published on 3 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-1853 and fix it if it is affected.\n\nWhat it is: CVE-2005-1853 is a high-severity vulnerability in n/a, published on 3 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-1853 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-1853/ (Markdown: https://insights.sbomify.com/CVE-2005-1853/index.md)","id":"CVE-2005-1853","markdown":"https://insights.sbomify.com/CVE-2005-1853/index.md","name":"CVE-2005-1853","record":{"aliases":["DEBIAN-CVE-2005-1853","DSA-770-1","GHSA-3823-wj6r-jpc9"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Gopher client","requires_auth":"low_privilege","summary":"Local attackers can exploit insecure temporary file creation in the Gopher client to escalate privileges on the system.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"debian","cpe":[{"product":"gopher","vendor":"university_of_minnesota"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"gopher.c in the Gopher client 3.0.5 does not properly create temporary files, which allows local users to gain privileges.","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":"Privilege escalation in n/a","id":"CVE-2005-1853","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2005"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2005-1854"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2005-1852"},"products":["n/a"],"published":"2005-08-03","related":[{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2005-2772","kev_date_added":null,"published":"2005-09-02"}],"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-16","vendors":["n/a"]},"summary":"Local attackers can exploit insecure temporary file creation in the Gopher client to escalate privileges on the system.","url":"https://insights.sbomify.com/CVE-2005-1853/"}