{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2004-2197 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-2197 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-2197 is a high-severity vulnerability in n/a, published on 10 Jul 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-2197 and fix it if it is affected.\n\nWhat it is: CVE-2004-2197 is a high-severity vulnerability in n/a, published on 10 Jul 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-2004-2197 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-2004-2197/ (Markdown: https://insights.sbomify.com/CVE-2004-2197/index.md)","id":"CVE-2004-2197","markdown":"https://insights.sbomify.com/CVE-2004-2197/index.md","name":"CVE-2004-2197","record":{"aliases":["GHSA-jxmr-g8ww-c5g5"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"KDE desktop utility","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary programs due to improper file ownership checks in kdocker, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kdocker","vendor":"kdocker"}],"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":"kdocker.cpp in kdocker 0.1 through 0.8 does not properly check the ownership of files, which could allow local users to execute arbitrary programs.","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":"Privilege escalation in n/a","id":"CVE-2004-2197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2004"},"n_packages":0,"n_references":7,"next":{"headline":"Missing authorization in n/a","id":"CVE-2004-2198"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2004-2196"},"products":["n/a"],"published":"2005-07-10","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-08","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary programs due to improper file ownership checks in kdocker, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2004-2197/"}