{"answers":{"affected":"It affects 6 products.","exploited":"There is no known exploitation of CVE-2006-6623 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-6623 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6623 is a high-severity vulnerability in n/a, published on 18 Dec 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-6623 and fix it if it is affected.\n\nWhat it is: CVE-2006-6623 is a high-severity vulnerability in n/a, published on 18 Dec 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-6623 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-6623/ (Markdown: https://insights.sbomify.com/CVE-2006-6623/index.md)","id":"CVE-2006-6623","markdown":"https://insights.sbomify.com/CVE-2006-6623/index.md","name":"CVE-2006-6623","record":{"aliases":["GHSA-63q6-7688-27w9"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Personal Firewall","requires_auth":"low_privilege","summary":"Local attackers can bypass Sygate Personal Firewall controls by spoofing Process Environment Block fields, allowing unauthorized process execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"antivirus_plus_firewall","vendor":"avg"},{"product":"comodo_personal_firewall","vendor":"comodo"},{"product":"personal_firewall","vendor":"filseclab"},{"product":"antihook","vendor":"infoprocess"},{"product":"look_n_stop","vendor":"soft4ever"},{"product":"sygate_personal_firewall","vendor":"symantec"}],"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":"Sygate Personal Firewall 5.6.2808 relies on the Process Environment Block (PEB) to identify a process, which allows local users to bypass the product's controls on a process by spoofing the (1) ImagePathName, (2) CommandLine, and (3) WindowTitle fields in the PEB.","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":"Security feature bypass in n/a","id":"CVE-2006-6623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2006"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2006-6624"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2006-6622"},"products":["n/a"],"published":"2006-12-18","related":[{"cvss_score":7.2,"headline":"Security feature bypass in n/a","id":"CVE-2006-6618","kev_date_added":null,"published":"2006-12-18"},{"cvss_score":7.2,"headline":"Security feature bypass in n/a","id":"CVE-2006-6619","kev_date_added":null,"published":"2006-12-18"},{"cvss_score":7.2,"headline":"Security feature bypass in n/a","id":"CVE-2006-6620","kev_date_added":null,"published":"2006-12-18"},{"cvss_score":7.2,"headline":"Security feature bypass in n/a","id":"CVE-2006-6621","kev_date_added":null,"published":"2006-12-18"},{"cvss_score":7.2,"headline":"Security feature bypass in n/a","id":"CVE-2006-6622","kev_date_added":null,"published":"2006-12-18"}],"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 bypass Sygate Personal Firewall controls by spoofing Process Environment Block fields, allowing unauthorized process execution.","url":"https://insights.sbomify.com/CVE-2006-6623/"}