# CVE-2010-3611: Null dereference in n/a

> Remote attackers can crash the ISC DHCP server by sending a malformed DHCPv6 Relay-Forward packet, causing a denial of service.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** Yes
- **Published:** 4 Nov 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-3611, GHSA-3q9m-cg52-56rj, RHSA-2010:0923

## What is CVE-2010-3611?

CVE-2010-3611 is a medium-severity vulnerability in n/a, published on 4 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ISC DHCP server 4.0 before 4.0.2, 4.1 before 4.1.2, and 4.2 before 4.2.0-P1 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via a DHCPv6 packet containing a Relay-Forward message without an address in the Relay-Forward link-address field.

## Which versions are affected by CVE-2010-3611?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dhclient` | Red Hat:enterprise_linux:6::client | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp` | Red Hat:enterprise_linux:6::client | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp-devel` | Red Hat:enterprise_linux:6::client | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhclient` | Red Hat:enterprise_linux:6::computenode | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp` | Red Hat:enterprise_linux:6::computenode | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhclient` | Red Hat:enterprise_linux:6::server | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp` | Red Hat:enterprise_linux:6::server | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp-devel` | Red Hat:enterprise_linux:6::server | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhclient` | Red Hat:enterprise_linux:6::workstation | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp` | Red Hat:enterprise_linux:6::workstation | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 12:4.1.1-12.P1.el6_0.1 |
| `dhcp-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 12:4.1.1-12.P1.el6_0.1 |

Products: Isc Dhcp.

## How do I fix CVE-2010-3611?

Upgrade to a fixed version.

## Is CVE-2010-3611 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0692](https://insights.sbomify.com/CVE-2009-0692/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-0413](https://insights.sbomify.com/CVE-2011-0413/): Denial of service in n/a (high 7.8)
- [CVE-2018-5732](https://insights.sbomify.com/CVE-2018-5732/): A specially constructed response from a malicious server can cause a buffer overflow in dhclient (high 7.5)
- [CVE-2009-1893](https://insights.sbomify.com/CVE-2009-1893/): Path traversal in n/a (medium 6.9)
- [CVE-2011-4868](https://insights.sbomify.com/CVE-2011-4868/): Null dereference in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3611 and fix it if it is affected.

What it is: CVE-2010-3611 is a medium-severity vulnerability in n/a, published on 4 Nov 2010. 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-2010-3611 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-2010-3611/ (Markdown: https://insights.sbomify.com/CVE-2010-3611/index.md)
```

## Sources

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

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