# CVE-2006-2450: Auth bypass in n/a

> Remote attackers can bypass authentication in LibVNCServer by requesting an insecure security type not offered by the server.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2450, GHSA-ghjj-rq7v-wjhm

## What is CVE-2006-2450?

CVE-2006-2450 is a high-severity authentication bypass vulnerability in n/a, published on 14 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

auth.c in LibVNCServer 0.7.1 allows remote attackers to bypass authentication via a request in which the client specifies an insecure security type such as "Type 1 - None", which is accepted even if it is not offered by the server, a different issue than CVE-2006-2369.

## Which versions are affected by CVE-2006-2450?

It affects 1 product.


Products: Libvncserver Libvncserver.

## How do I fix CVE-2006-2450?

Upgrade to a fixed version.

## Is CVE-2006-2450 being exploited?

There is no known exploitation of CVE-2006-2450 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2450 and fix it if it is affected.

What it is: CVE-2006-2450 is a high-severity authentication bypass vulnerability in n/a, published on 14 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2450 in the wild and no public exploit code.

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-2006-2450/ (Markdown: https://insights.sbomify.com/CVE-2006-2450/index.md)
```

## Sources

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

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