{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2073 exists.","fix":"No fix has been published for CVE-2004-2073 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-2073 is a high-severity vulnerability in n/a, published on 19 May 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-2004-2073 and fix it if it is affected.\n\nWhat it is: CVE-2004-2073 is a high-severity vulnerability in n/a, published on 19 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2073 exists.\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-2004-2073/ (Markdown: https://insights.sbomify.com/CVE-2004-2073/index.md)","id":"CVE-2004-2073","markdown":"https://insights.sbomify.com/CVE-2004-2073/index.md","name":"CVE-2004-2073","record":{"aliases":["GHSA-q2m5-737c-xfjv"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux virtualization","requires_auth":"high_privilege","summary":"Local root users in Linux-VServer can escape the virtual server sandbox to access the host filesystem via a modified chroot exploit.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"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":"Linux-VServer 1.24 allows local users with root privileges on a virtual server to gain access to the filesystem outside the virtual server via a modified chroot-again exploit using the chmod command.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2004-02-06","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2004-02-06","kind":"exploitdb","ref":"23658","stars":null,"title":"Linux VServer Project 1.2x - Chroot Breakout"}],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2004-2073","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2004"},"n_packages":0,"n_references":6,"next":{"headline":"Denial of service in n/a","id":"CVE-2004-2074"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2004-2072"},"products":["n/a"],"published":"2005-05-19","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Local root users in Linux-VServer can escape the virtual server sandbox to access the host filesystem via a modified chroot exploit.","url":"https://insights.sbomify.com/CVE-2004-2073/"}