{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-0229 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-0229 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0229 is a low-severity vulnerability in n/a, published on 17 Jan 2006. 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-2006-0229 and fix it if it is affected.\n\nWhat it is: CVE-2006-0229 is a low-severity vulnerability in n/a, published on 17 Jan 2006. 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-2006-0229 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-2006-0229/ (Markdown: https://insights.sbomify.com/CVE-2006-0229/index.md)","id":"CVE-2006-0229","markdown":"https://insights.sbomify.com/CVE-2006-0229/index.md","name":"CVE-2006-0229","record":{"aliases":["GHSA-jhv8-9x2f-v225"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Wehntrust application","requires_auth":"low_privilege","summary":"Local attackers can gain privileges by placing a malicious executable in the C: drive, exploiting an unquoted search path in Wehntrust.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wehntrust","vendor":"wehnus"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"Unquoted Windows search path vulnerability in Wehntrust might allow local users to gain privileges via a malicious \"program.exe\" file in the C: folder, which is run when Wehntrust creates the autostart key.","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-2006-0229","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2006"},"n_packages":0,"n_references":5,"next":{"headline":"Auth bypass in n/a","id":"CVE-2006-0230"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2006-0228"},"products":["n/a"],"published":"2006-01-17","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":"Local attackers can gain privileges by placing a malicious executable in the C: drive, exploiting an unquoted search path in Wehntrust.","url":"https://insights.sbomify.com/CVE-2006-0229/"}