# CVE-2007-0756: Null dereference in n/a

> Remote attackers can crash the Chicken of the VNC client by sending a malformed ServerInit packet with an oversized computer name.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8q68-54jr-f7ph

## What is CVE-2007-0756?

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.

### Official 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.

## Which versions are affected by CVE-2007-0756?

It affects 1 product.


Products: Chicken of the Vnc Chicken of the Vnc.

## How do I fix CVE-2007-0756?

No fix has been published for CVE-2007-0756 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-0756 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0756 exists.

Public exploit code:

- Chicken of the VNC 2.0 - 'NULL-pointer' Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0756 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0756 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2007-0756/ (Markdown: https://insights.sbomify.com/CVE-2007-0756/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-0756
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-0756
- OSV: https://osv.dev/vulnerability/CVE-2007-0756

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-0756/
Summaries are generated and may contain mistakes; the official description above is the record.