{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0756 exists.","fix":"No fix has been published for CVE-2007-0756 yet. Limit exposure of the affected software until one is available.","what":"CVE-2007-0756 is a high-severity vulnerability in n/a, published on 6 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2007-0756 and fix it if it is affected.\n\nWhat it is: CVE-2007-0756 is a high-severity vulnerability in n/a, published on 6 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0756 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-2007-0756/ (Markdown: https://insights.sbomify.com/CVE-2007-0756/index.md)","id":"CVE-2007-0756","markdown":"https://insights.sbomify.com/CVE-2007-0756/index.md","name":"CVE-2007-0756","record":{"aliases":["GHSA-8q68-54jr-f7ph"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"VNC client","requires_auth":"none","summary":"Remote attackers can crash the Chicken of the VNC client by sending a malformed ServerInit packet with an oversized computer name.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"chicken_of_the_vnc","vendor":"chicken_of_the_vnc"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:C","version":"2.0"},"cwes":[],"description":"Chicken of the VNC (cotv) 2.0 allows remote attackers to cause a denial of service (application crash) via a large computer-name size value in a ServerInit packet, which triggers a failed malloc and a resulting NULL dereference.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2007-02-02","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2007-02-02","kind":"exploitdb","ref":"3257","stars":null,"title":"Chicken of the VNC 2.0 - 'NULL-pointer' Remote Denial of Service"}],"tier":"weaponised"},"has_fix":null,"headline":"Null dereference in n/a","id":"CVE-2007-0756","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2007"},"n_packages":0,"n_references":7,"next":{"headline":"Code injection in n/a","id":"CVE-2007-0757"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2007-0754"},"products":["n/a"],"published":"2007-02-06","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-07","vendors":["n/a"]},"summary":"Remote attackers can crash the Chicken of the VNC client by sending a malformed ServerInit packet with an oversized computer name.","url":"https://insights.sbomify.com/CVE-2007-0756/"}