# CVE-2006-0105: Denial of service in n/a

> Remote attackers can cause a denial of service in PostgreSQL on Windows by sending many simultaneous connection requests, requiring an upgrade.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f2vf-wm7c-xq6f

## What is CVE-2006-0105?

CVE-2006-0105 is a medium-severity denial of service vulnerability in Postgresql Postgresql, published on 10 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PostgreSQL 8.0.x before 8.0.6 and 8.1.x before 8.1.2, when running on Windows, allows remote attackers to cause a denial of service (postmaster exit and no new connections) via a large number of simultaneous connection requests.

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

It affects 1 product.


Products: Postgresql Postgresql.

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

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

## Is CVE-2006-0105 being exploited?

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

## Other vulnerabilities in Postgresql Postgresql

- [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0)
- [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0)
- [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0)
- [CVE-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0)
- [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0105 is a medium-severity denial of service vulnerability in Postgresql Postgresql, published on 10 Jan 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-0105 in the wild and no public exploit code.

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

## Sources

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

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