{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-6227 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-6227 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6227 is a medium-severity vulnerability in n/a, published on 2 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-6227 and fix it if it is affected.\n\nWhat it is: CVE-2006-6227 is a medium-severity vulnerability in n/a, published on 2 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-6227 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-6227/ (Markdown: https://insights.sbomify.com/CVE-2006-6227/index.md)","id":"CVE-2006-6227","markdown":"https://insights.sbomify.com/CVE-2006-6227/index.md","name":"CVE-2006-6227","record":{"aliases":["GHSA-r2f6-wx3g-r4jw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"NeoEngine library","requires_auth":"none","summary":"Remote attackers can crash the NeoEngine application by sending a message with an excessively large length, causing a null pointer dereference.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"neoengine","vendor":"neoengine"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"The Core::Receive function in neonet/core.cpp for NeoEngine 0.8.2 and earlier, and CVS 3422, allow remote attackers to cause a denial of service (engine crash) via a message with a large uiMessageLength that produces a failed memory allocation and a null pointer dereference.","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":"Null dereference in n/a","id":"CVE-2006-6227","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2006"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-6228"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2006-6226"},"products":["n/a"],"published":"2006-12-02","related":[{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2006-6226","kev_date_added":null,"published":"2006-12-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-08-07","vendors":["n/a"]},"summary":"Remote attackers can crash the NeoEngine application by sending a message with an excessively large length, causing a null pointer dereference.","url":"https://insights.sbomify.com/CVE-2006-6227/"}